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
There are a handful of yaml schemas with something like: https://github.com/zalando/connexion/blob/f31ac615bfc8a3c696c5ebe53f3c57e5234ff6f8/examples/openapi3/helloworld/openapi/helloworld-api.yaml#L15-L16 pyyaml interprets these keys as integers, while the OpenAPI specification requires that they be strings: https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#format
The above should be replaced with
responses: '200':
openapi-spec-validator does not validate this, but instead coerces int keys to str.
int
str
The text was updated successfully, but these errors were encountered:
I think the support for coercing int to str is from swagger2.
Sorry, something went wrong.
Change response codes to strings (spec-first#1112)
7fc9d68
a48949c
Successfully merging a pull request may close this issue.
There are a handful of yaml schemas with something like:
https://github.com/zalando/connexion/blob/f31ac615bfc8a3c696c5ebe53f3c57e5234ff6f8/examples/openapi3/helloworld/openapi/helloworld-api.yaml#L15-L16
pyyaml interprets these keys as integers, while the OpenAPI specification requires that they be strings:
https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#format
The above should be replaced with
openapi-spec-validator does not validate this, but instead coerces
int
keys tostr
.The text was updated successfully, but these errors were encountered: