We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Written in yaml because json is exhausting
someObject: type: object property: nullableProperty: oneOf: - type: "null" - type: object properties: yay: type: string
Resulting output (Incorrect )
someObject: type: object property: nullableProperty: oneOf: - nullable: true - type: object properties: yay: type: string
Expected Output (correct)
someObject: type: object property: nullableProperty: type: object nullable: true properties: yay: type: string
While this will validate (loosely) against Swagger 3.0 specification, it will indeed break code generators.
The text was updated successfully, but these errors were encountered:
I dunno if this is the most common use case? I’ve never seen this :)
Could you get a PR going?
Sorry, something went wrong.
Exactly, as JSON Schema supports an array for type, the oneOf is pretty redundant.
type
oneOf
You're absolutely right :)
No branches or pull requests
Written in yaml because json is exhausting
Resulting output (Incorrect )
Expected Output (correct)
While this will validate (loosely) against Swagger 3.0 specification, it will indeed break code generators.
The text was updated successfully, but these errors were encountered: