Use updated name for HTTP 422 ("Unprocessable Content") in JSON error response schema#598
Open
arcanemachine wants to merge 1 commit intoopen-api-spex:masterfrom
Open
Use updated name for HTTP 422 ("Unprocessable Content") in JSON error response schema#598arcanemachine wants to merge 1 commit intoopen-api-spex:masterfrom
arcanemachine wants to merge 1 commit intoopen-api-spex:masterfrom
Conversation
The newest RFC on HTTP Semantics (RFC 9110) no longer uses the term `Unprocessable Entity` when describing HTTP 422, but now refers to it as `Unprocessable Content`. This commit updates the default JSON error response schema to reflect this change. Ref: https://httpwg.org/specs/rfc9110.html#status.422
Contributor
|
Following the discussion in elixir-plug/plug#1174 since this PR does not require any client changes we can consider it non-breaking. |
zorbash
approved these changes
Mar 15, 2024
Contributor
|
[Suggestion] Update the references to |
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
2 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.
The newest RFC on HTTP Semantics (RFC 9110) no longer uses the term
Unprocessable Entitywhen describing HTTP 422, but now refers to it asUnprocessable Content.This commit updates the default JSON error response schema to reflect this change.
Fixes #599
https://httpwg.org/specs/rfc9110.html#status.422