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
Even it's not released yet, in OpenAPI 3.1 Specification, there will be support for the type: 'null' property within schemas (see also JSON Schema Draft 2019-09). It seems that the parser doesn't support this for now because using swagger-cli tool, the schema validation fails with the message:
Data does not match any schemas from 'oneOf' at #/paths//pets/{id}/put/requestBody/content/application/json/schema
Data does not match any schemas from 'oneOf' at #/content/application/json/schema/properties/nullProp
No enum match for: null at #/properties/nullProp/type
Missing required property: $ref at #/properties/nullProp
Missing required property: $ref at #/content/application/json/schema
Missing required property: $ref at #/paths//pets/{id}/put/requestBody
I'm not sure how strict the parser (and its validation) would be, but it would be nice to support "null" type there. Thanks
The text was updated successfully, but these errors were encountered:
Even it's not released yet, in OpenAPI 3.1 Specification, there will be support for the
type: 'null'
property within schemas (see also JSON Schema Draft 2019-09). It seems that the parser doesn't support this for now because using swagger-cli tool, the schema validation fails with the message:I'm not sure how strict the parser (and its validation) would be, but it would be nice to support
"null"
type there. ThanksThe text was updated successfully, but these errors were encountered: