Necessary to test all API actions.

Necessary to start translating API responses by defining shared text which can be reused across multiple actions. Using the api.shared namespace to house all of this.

Necessary to define custom properties. Will, initially, be used for border animations.

The bit-loader class was refactored to pass in --angle for rotation so the loader will remain rotating in an infinite loop.

Necessary to create a new extension exchange.

Necessary to delete an existing extension exchange.

Necessary to list all extension exchanges.

Necessary to update an existing extension exchange.

Necessary to show an extension exchange.

Provides a nice fallback, for older devices, when all you have is battery voltage information. Anything above 4.2 means the device is charging. This allows us to show charging status for a much broader range of devices now.

Necessary to create an extension exchange. Will soon be used by the API create action.

Necessary to encapsulate the creation of a new exchange. Will soon be used for UI and API purposes.

Necessary to encapsulate the deletion of an existing exchange. Will soon be used for UI and API purposes.

Necessary to patch an existing extension exchange. Will soon be used by API patch action.

Necessary to serialize an extension exchange in API responses. Will soon be used by all related API actions.

Necessary to encapsulate the updating of an exsiting exchange. Will soon be used for UI and API purposes.

Necessary to explain what this endpoint is and how to use it.

A small quality of life improvement when wanting to jump between related documentation.

Necessary to provide translations for known keys. More to do here but makes a good dent.

Necessary to define robot behavior. This includes allowing this file to be checked into Git and ensuring Rack can serve the file.

Helps indicate which item is active when hovering by transitioning the appearance of the border in 0.3 seconds and then using a conic gradient to render a wheel of five colors to create a pulsing effect. Would prefer to use border-image (less code) but it won’t honor border radius so am using psuedo elements to pull this off by insetting one inside the other to create the illusion of a border.

This came out of an issue discussion where it was slightly confusing as to how the MAC address and API keys work. This new information helps shed more light on how each of these work and how best to use them.

A small set of clarifications.

Necessary for consistent design with existing creator and updater siblings. This also ensures the ID is of the right type as well.

Weekly maintenance and upkeep.

Weekly updates and general maintenance.

Now that we have the --angle property, we can update the keyframe so that the property can be animated without changing behavior of existing spinners.

Details.

Details.

Details:

• Shrine.

• Zip.

Details. This also picks up Code Mirror patches.

Details.

Necessary to reduce confusion and improve readability.

Necessary to address this warning that popped up after upgrading to Roda 3.108.0:

:content_type_regexp option not provided to json_parser plugin, using /json/ for backwards compatibility, which may be insecure, using /\Aapplication\/json\b/i or /\Aapplication\/(?:vnd\.api\+)?json\b/i is recommended

The above will become the default in Roda 4.0.0.

Ensures both deadlines are disabled when session_expiration_enabled is false so that JWT tokens never expire. Otherwise, the default deadlines will eventually cause the JWT tokens to expire.

RuboCop was updated to ignore the long block length due to the poor design of Rodauth using very long blocks for configuration purposes.

Necessary to ensure the Redis cache is cleared because we are using Redis despite never writing data to PostgreSQL. This helps reduce random spec failures due to Redis not being reset.

Necessary to more strictly adhere to what the Core implementation uses for calculating battery percent based on voltage. The API documentation was fixed to show the voltage range as well.

Reek has been updated to ignore feature envy, in this case, because we only refer to raw twice.

Missed this when working on 83221a3 (Fixed device struct battery percentage calculation), earlier, where a range for negative numbers is more elegant than the guard check. Both RuboCop and Reek have been updated accordingly.

Accidentally forgot to use a struct instead of a database record since we don’t need the database for this spec. This ensures no other specs are effected by data that isn’t cleaned up properly.

Necessary to resolve RuboCop issues and reduce duplication now that we have a translation for this message.

Necesssary to match how actions are organized for consistency and improved lookup.

Necessary to reduce duplication so we can use the same object for UI and API purposes.

Necessary to reduce duplication so we can use the same object for UI and API purposes.

Necessary to reduce duplication so we can use the same object for UI and API purposes.