Fix kitchen_sink options flow defaults #129503
Closed
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.
Proposed change
Kitchen sink options flow sections demo was not correctly restoring the previously saved values (even though it seemed to be attempting to do so). I have fixed this to retrieve the previously saved value.
Add a select selector for purposes of testing Config Flow: SelectSelectorConfig does not display the saved selected item inside a section frontend#22590, also to exhibit an example usage of selectors and more translations in config flow sections.
Fix hassfest script which was blocking me from adding a data_description to a section, which I believe should be allowed per https://developers.home-assistant.io/docs/data_entry_flow_index#labels--descriptions
Type of change
Additional information
Checklist
ruff format homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
.To help with the load of incoming pull requests: