Use ConfigEntry runtime_data in detailed hello world #70
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
MartinHjelmare
requested changes
Aug 17, 2024
|
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
MartinHjelmare
changed the title
HipsterBrown
force-pushed
the
nhehr/config_entry_runtime_data
branch
from
5b32f0c to
6816f75
Compare
|
Thanks for the review, @MartinHjelmare! 👍 |
|
CI failure is unrelated. |
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.
Based on the change to the
ConfigEntryusage described in this developer docs blog post, integrations can/should extend theConfigEntrytype to store custom data as theruntime_datafield to be accessed by platforms and services associated with that entry.This PR updates the
detailed_hello_world_pushexample to demonstrate this new pattern.