Starting move of history_stats to integration key for ADR0007 #120876
+325
−44
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
Allow to define history_stats under
history_stats:
configuration key instead ofsensor:/platform:
.If I understand the rules correctly, this must be done before any future enhancements to the yaml options. ( e.g. from comment: #104907 (review))
Borrowed heavily from #92824 for inspiration.
I think a lot of work could be done still on testing, such as moving more existing tests to the integration key style (right now only have one), but wanted to put this up to get any early feedback if this PR would be welcomed, and if this is the right direction to go.
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
..coveragerc
.To help with the load of incoming pull requests: