Repository navigation
fix(jsonapi): document non-exposed relations in included schema - #8734
Merged
soyuka merged 1 commit intoOct 19, 2026
Merged
Conversation
Related resources whose only operation is NotExposed were dropped from the included anyOf, leaving an empty (invalid) anyOf although the serializer emits them. Reference their own definition like any other target. Fixes api-platform#8700
soyuka
force-pushed
the
fix/jsonapi-included-notexposed-8700
branch
from
October 19, 2026 12:17
0434cc2 to
475bcac
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 skipped related classes whose only operation is
NotExposedwhen buildingincluded, which gaveanyOf: [](invalid JSON Schema) for a relation to such a resource, and an incompleteanyOffor a polymorphic relation mixing exposed and non-exposed targets. The serializer does emit them inincluded(e.g.Product.aggregateRatingwith?include=aggregateRating), so the schema now references their own definition like any other target.The
canRead()skip dates back to #5501, which #5722 fixed in metadata (generatedNotExposedoperations inherit the resource options), the #5501 schema test still passes.