Skip to content
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

Support integers as status codes #7

Merged
merged 1 commit into from Jul 27, 2019

Conversation

killercup
Copy link
Contributor

@killercup killercup commented Jun 24, 2019

Took a bit of digging but dtolnay was able to figure out how to support
allowing both strings and integers for status codes. This means that we
can now parse OpenAPI specs that are written in a more lenient way, i.e.
without a bunch of quotes in YAML.

Since all the fixtures are real specs (AFAICT), I didn't want to change
them and only added unit tests.

Took a bit of digging but dtolnay was able to figure out how to support
allowing both strings and integers for status codes. This means that we
can now parse OpenAPI specs that are written in a more lenient way, i.e.
without a bunch of quotes in YAML.

Since all the fixtures are real specs (AFAICT), I didn't want to change
them and only added unit tests.
@glademiller glademiller merged commit 1b91c2e into glademiller:master Jul 27, 2019
JamesHinshelwood pushed a commit to JamesHinshelwood/openapiv3 that referenced this pull request Aug 27, 2021
JamesHinshelwood pushed a commit to JamesHinshelwood/openapiv3 that referenced this pull request Apr 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants