Uh oh!
There was an error while loading. Please reload this page.
v3.3: describe stringified response codes without referencing a specific formaat - #5332
Merged
ralfhandl merged 2 commits intoJun 9, 2026
Merged
Conversation
Uh oh!
There was an error while loading. Please reload this page.
handrews
approved these changes
May 13, 2026
karenetheridgeforce-pushed
the
ether/v3.3-response-code-markup
branch
from
May 20, 2026 22:37
a826a0b to
be80eafComparekarenetheridgeforce-pushed
the
ether/v3.3-response-code-markup
branch
2 times, most recently
from
June 4, 2026 00:10
597bad0 to
6d24c34Compare…rmat In JSON, property keys are always strings; in YAML they may or not be depending on the parser, but other formats may also be in use (TOML, TOON etc). What matters is the resulting type(s) of the decoded data, not the specific formatting used for the serialized form.
Co-authored-by: Henry Andrews <andrews_henry@yahoo.com>
karenetheridgeforce-pushed
the
ether/v3.3-response-code-markup
branch
from
June 9, 2026 01:11
6d24c34 to
f52c4a6Compareralfhandl
approved these changes
Jun 9, 2026
Uh oh!
There was an error while loading. Please reload this page.
1 task
karenetheridge added a commit
to karenetheridge/OpenAPI-Specification
that referenced
this pull request
Jul 8, 2026
…rmat (OAI#5332) In JSON, property keys are always strings; in YAML they may or not be depending on the parser, but other formats may also be in use (TOML, TOON etc). What matters is the resulting type(s) of the decoded data, not the specific formatting used for the serialized form.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
In JSON, property keys are always strings; in YAML they may or not be depending on the parser, but other formats may also be in use (TOML, TOON etc). What matters is the resulting type(s) of the decoded data, not the specific formatting used for the serialized form.