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
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
We use our openapi 3.0.1 specs to automatically generate mocks and run contract tests. These contract tests include testing that the implementing server correctly validates requests and returns expected 400 Bad Request responses. This means we have examples in our docs of invalid requests. We cannot use swagger-cli validate, but would like to, because the validation fails on examples that don't adhere to the schema.
Ideal behavior would be to either be able to mark an example somehow to ignore validation for it, or pass an argument or configuration into swagger-cli validate to bypass validation of certain examples.
I will attempt to create a minimal schema to illustrate the issue.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We use our openapi 3.0.1 specs to automatically generate mocks and run contract tests. These contract tests include testing that the implementing server correctly validates requests and returns expected 400 Bad Request responses. This means we have examples in our docs of invalid requests. We cannot use swagger-cli validate, but would like to, because the validation fails on examples that don't adhere to the schema.
Ideal behavior would be to either be able to mark an example somehow to ignore validation for it, or pass an argument or configuration into swagger-cli validate to bypass validation of certain examples.
I will attempt to create a minimal schema to illustrate the issue.
The text was updated successfully, but these errors were encountered: