OpenAPI: Quote HTTP response status code keys - #17839
Open
yangshangqing95 wants to merge 1 commit into
Open
Conversation
gaborkaszab
reviewed
Aug 28, 2026
gaborkaszab
left a comment
gaborkaszab
left a comment
Contributor
There was a problem hiding this comment.
I'm not entirely sure this adds any extra value to the spec TBH.
uros-b
reviewed
Aug 28, 2026
uros-b
left a comment
uros-b
left a comment
Member
There was a problem hiding this comment.
Thank you @yangshangqing95 - seems like a correct and complete spec compliance fix, will leave up to REST/OpenAPI spec experts to examine further
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Quotes HTTP response status code keys, including numeric and wildcard responses such as
'200'and'5XX'.The OpenAPI 3.1.1 Responses Object specification requires response status code keys to be enclosed in quotation marks for JSON and YAML compatibility.
This change does not modify any response definitions or schemas.