As an average user who is not completely familiar with the intricacies of JSON Schema <≠> OpenAPI and the differences between OpenAPI v2 and v3, I often mix up JSON Schema, OAS2 and OAS3 keywords like anyOf and oneOf, so please let me know when I put the wrong keyword in the wrong place.
Is your feature request related to a problem?
API description documents should conform to the description format in question, as putting invalid keywords in those documents can lead to inconsistent behavior across various tools that might mistakenly support those keywords. Other tooling which is actually compliant will then look like its failing.
Describe the solution you'd like
The rule should error if an anyOf, oneOf or not appears in OpenAPI v2, but anyOf is in fact allowed.
The text was updated successfully, but these errors were encountered: