Fix excessive rerendering of history charts #8340
Merged
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.
Breaking change
Proposed change
Closes #8274
When @spacegaier reimplemented the history chart as LitElement, that unfortunately broke their tooltips because the chart would rerender on every change of the hass object. In my case that was every 500 ms and I'm not able to read that fast.
This PR implements shouldUpdate so the chart only rerenders when there was either a change to its own entity or the underlying history data.
Type of change
Example configuration
Additional information
Checklist
If user exposed functionality or configuration variables are added/changed: