Clarify YAML reloading config header #4835
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
So both person and zone would crash if you didn't have person/zones in your YAML and called the reload service. Both times it was reported by someone who did not use YAML to config either but somehow thought they had to call the reload functions.
This PR clarifies header/description. Suggestons on improvements for this welcome.
Type of change
Example configuration
Additional information
Checklist
If user exposed functionality or configuration variables are added/changed: