Repository navigation
fix(jsonapi): split schema relationships on the input/output class - #8728
Merged
soyuka merged 2 commits intoOct 19, 2026
Merged
Conversation
The attributes/relationships split was computed on the resource class, so an input DTO property holding plain objects was documented as resource linkage while the denormalizer reads it from attributes. Fixes api-platform#8698
soyuka
force-pushed
the
fix/jsonapi-input-dto-collection-8698
branch
from
October 19, 2026 12:13
098b2b7 to
c11090b
Compare
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.
The JSON:API schema factory decided what goes under
attributesvsrelationshipsfrom the resource class, so an input DTO property holding plain objects was documented as resource linkage, while the denormalizer reads it fromattributes. The split now uses the input/output class, which is also what the normalizer uses at runtime for output DTOs.Covered with a unit test: with jsonld enabled, Hydra's schema factory currently rewrites every input schema request to
jsonbefore the JSON:API factory runs, so JSON:API input schemas can't be observed through the functional kernel. That's a separate bug, fixed in a follow-up PR.