Repository navigation
fix(jsonapi)!: drop non-spec type member from error objects - #8732
Merged
soyuka merged 2 commits intoOct 19, 2026
Merged
Conversation
JSON:API 1.1 forbids additional members on objects it defines, error objects only define links.type. The problem type URI was already exposed there, the top-level copy is removed. Refs api-platform#8704
soyuka
marked this pull request as ready for review
October 19, 2026 12:13
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
1 participant
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.
JSON:API error objects carry a top-level
typenext tolinks.type. JSON:API 1.1 (https://jsonapi.org/format/#document-structure): "Unless otherwise noted, objects defined by this specification or any applied extensions MUST NOT contain any additional members.", error objects only definelinks.type(https://jsonapi.org/format/#error-objects), which we already fill with the same value.Context: json-api/json-api#1787 (aligning with Problem Details), where the RFC
typemaps tolinks.type.Impact: clients reading
errors[].typemust readerrors[].links.type. Draft to see the impact, needs an UPGRADE note before merge. TheError.jsonapiOpenAPI schema still advertisestypethrough the sharedErrordefinition, left for a follow-up.