astarte-dashboard
astarte-dashboard copied to clipboard
astarte-platform
Astarte dashboard
In the current `master` branch (v1.2.0-dev) the device page registers to device events twice, probably due to a component rerender 
Currently the page that reports data exchanged through a device's interface only displays a list of values without much embellishment. We could evaluate a better layout and appropriate charts to...
It's currently possible to create triggers on data coming from an interface. To do so, the user navigates to the Trigger Editor, select an interface, and manually inputs the preferred...
We should evaluate clearly separating APIs designed for validating JSON definitions of resources from APIs designed for managing resources. This would allow the Dashboard to more easily compose the functionality...
Text editors (interfaces, triggers, trigger delivery policies) should allow modifying JSON definitions without failing the parsing/validating process. This would allow the Dashboard to work with Astarte APIs even though it...
The Dashboard employs simple textareas to display and modify the JSON definitions of interfaces, triggers and trigger delivery policies. The UX could be much improved by using actual text editors...
Since the JWT used for authentication directly contains the list of authorization claims, it can be evaluated how to hide or disable relevant parts of the UI when the permission...
Since server-owned interfaces are designed for handling data published via the Appengine API instead of published by devices, it can be valuable to improve the page that displays data for...
The idea here is that cookies provide better handling for the auth details, such as setting an expiry or letting users ergonomically purge their cookies to clear the auth details.
It should be verified that the Dashboard correctly queries Astarte to fetch the latest values of interfaces. For instance, it can be verified: - whether the Dashboard truncates the max...