-
-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
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
Failures in oneOf, anyOf, etc, are actually in the referenced schema #126
Comments
A workaround is to replace all refs with a simple object; then it will validate all of the schemata without getting tripped up by a ref. |
giang-nghg
added a commit
to Mykrobe-tools/mykrobe-atlas-tracking-api
that referenced
this issue
Aug 20, 2021
Zhicheng-Liu
pushed a commit
to Mykrobe-tools/mykrobe-atlas-tracking-api
that referenced
this issue
Aug 21, 2021
* Update OpenAPI generator * Delete sample endpoint * Fixed requirement to avoid currently open issue: python-openapi/openapi-spec-validator#126 * Change return status * Update specs
Is this fixed by #129? It can be tried easily using:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If a schema is invalid, it will cause a oneOf to fail instead of failing on its own. I discovered this while thinking
optional
was a valid thing.The below is valid except I've added
optional
toDog
. The failure is nowOn instance['paths']['/pets']['patch']['requestBody']
instead of the expected['components']['schemas']['Dog']
.The text was updated successfully, but these errors were encountered: