🐛 Fix JSON Schema accepting bools as valid JSON Schemas, e.g. additionalProperties: false
#9781
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.
🐛 Fix JSON Schema accepting bools as valid JSON Schemas, e.g.
additionalProperties: false
This solves: #9780
A "valid JSON Schema" includes a
bool
(i.e.true
andfalse
).additionalProperties
doesn't have to be a JSON object, it can befalse
, to mean no additional properties are allowed.When I upgraded the JSON Schema models to include the new types and fields for the new JSON Schema 2020-12 I removed
bool
as a valid JSON Schema.I reviewed all the spec again, this updates all the other fields that would allow
bool
as a valid value.