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
Was the commit 720e282 also meant to remove the name of the schema from the title for anyOf and oneOf?
Before:
After:
The relevant yaml:
any: anyOf: - $ref: "#/components/schemas/Foo" - $ref: "#/components/schemas/Bar" one: oneOf: - $ref: "#/components/schemas/Foo" - $ref: "#/components/schemas/Bar" all: allOf: - $ref: "#/components/schemas/Foo" - $ref: "#/components/schemas/Bar"
Foo: type: object properties: foo: type: string Bar: type: object properties: bar: type: string
The text was updated successfully, but these errors were encountered:
@fredriklengstrand no, it didn't mean so. Thanks for reporting. I will investigate.
Sorry, something went wrong.
fix: fix oneOf/anyOf titles
39b930d
fixes #618, #621
Fixed in 39b930d
No branches or pull requests
Was the commit 720e282 also meant to remove the name of the schema from the title for anyOf and oneOf?
Before:
After:
The relevant yaml:
The text was updated successfully, but these errors were encountered: