Entity historical data widget #4603
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PizzaMarinara
force-pushed
the
feature_entity_history
branch
from
6f0b133
to
2febb51
Compare
ivorsmorenburg
added a commit
to ivorsmorenburg/android
that referenced
this pull request
Sep 6, 2024
|
Hey @PizzaMarinara 👋 please let us know if you have any questions or would like any comments on the functionality. I know this PR is in draft but wanted to check in. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This is a proposed draft solution to have historical data of one or more entities in a simple widget.
The UI can definitely be corrected or made more user friendly, as now it's just a simple list of text strings.
The code uses the REST API
GET /api/history/period/<timestamp>found in the documentation here.Screenshots
Config:
Widget:
Link to pull request in Documentation repository
Documentation isn't implemented yet as this is still a rough draft of a tech implementation
Any other notes