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
My own use case would be to validate the schemas in the upcoming Open API 3.1 spec which are based on 2019-09. Historically OpenAPI has used a forked/incompatible variant of JSON Schema but with 3.1 it is a strict superset, meaning that any JSON Schema validator, like valijson, can be used for validating request payloads etc.
The text was updated successfully, but these errors were encountered:
I'll take a look at what will be involved. I haven't been following development of the spec, but if it's not too difficult to support it, I'm happy to do so.
My own use case would be to validate the schemas in the upcoming Open API 3.1 spec which are based on 2019-09. Historically OpenAPI has used a forked/incompatible variant of JSON Schema but with 3.1 it is a strict superset, meaning that any JSON Schema validator, like valijson, can be used for validating request payloads etc.
The text was updated successfully, but these errors were encountered: