-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate Statistic Card with Energy Date Picker #23794
Merged
MindFreeze
merged 4 commits into
home-assistant:dev
from
karwosts:statistic-card-date-picker
Feb 7, 2025
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
944fe8b
Support energy-date-selection for statistic card
karwosts 9a6c80c
Merge branch 'dev' of https://github.com/home-assistant/frontend into…
karwosts 8cccdfc
reuse period key
karwosts b93ff1c
Merge branch 'statistic-card-date-picker' of https://github.com/karwo…
karwosts File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This logic seems off. If you have
this._config.period === PERIOD_ENERGY
and change the entity, I thinkthis._setFetchStatisticTimer()
will be calledThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that's ok/intended.
_setFetchStatisticTimer
fetches the statistic, and then schedules the timer only if period !== PERIOD_ENERGY. If it is using energy mode it will continue being subscribed to the energy callback.To be honest I'm not even sure if anything in this function even really matters... it looks like changing anything in the config destroys the entire card element and rebuilds a new one from scratch. Like every time I touch the config I see
disconnectedCallback
andfirstUpdated
in hui-statistic-card being called again. I didn't think that was supposed to happen, seems odd. Of course would still like to get it to be correct, but that surprised me.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Recreating the card makes sense to me to avoid all this. But now I wonder why we bother with this update logic in all the cards. Perhaps custom things like
config-template-card
trigger this.Anyway, approving this since it works.