You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In most circumstances it's not preferable to allow additional (unknown) string-indexed keys on your schemas. Currently, sometimes, those can pop up because of processing that leaves "type": "object" without additionalProperties: false.
It would be nice to have an option to blanket enable additionalProperties, always. This would also be helpful, because the default for additionalProperties is true when left blank.
The text was updated successfully, but these errors were encountered:
In most circumstances it's not preferable to allow additional (
unknown
) string-indexed keys on your schemas. Currently, sometimes, those can pop up because of processing that leaves"type": "object"
withoutadditionalProperties: false
.It would be nice to have an option to blanket enable
additionalProperties
, always. This would also be helpful, because the default foradditionalProperties
istrue
when left blank.The text was updated successfully, but these errors were encountered: