Use updated name for HTTP 422 ("Unprocessable Content") in JSON error response schema #598
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 Entity
when 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