Allow nested dictionary to be optional in addon config #4607
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
See this issue for more details on the behavior I am trying to enable along with an example: #4606
I believe that if a nested dictionary is in the
schema
but not in theoptions
and therefore hidden by default from the configuration UI, it should be optional, and I consider this a bug because you can hide it.I know I need to refactor tests significantly for this change, but I wanted to get a sense of whether I am headed in the right direction before I continue.
I also attempted to improve the error message because I noticed that the
key
that failed validation is not always part of the message which makes it confusing.Type of change
Additional information
Checklist
black --fast supervisor tests
)If API endpoints of add-on configuration are added/changed: