Repository navigation
fix(jsonapi): check relation IRI type on denormalization - #8788
Merged
Merged
Conversation
The JSON:API relation denormalizer resolved IRIs directly through the IRI converter, bypassing the resource type check applied to other formats.
This was referenced Nov 4, 2026
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
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 JSON:API
denormalizeRelation()called the IRI converter directly, so the relation type check done inAbstractItemNormalizer::getResourceFromIri()never ran for JSON:API payloads. It now goes through the same method (made protected). Not found relations now behave like JSON-LD (UnexpectedValueException,denormalize_throw_on_relation_not_foundhonored).