fix(serializer): resolve IRIs on borrowed routes - #8521
Open
soyuka wants to merge 1 commit into
Open
Conversation
Dispatch relation IRIs through the expected resource operation when it explicitly borrows the matched route. Keep unrelated route owners subject to the existing type guard. Fixes api-platform#8503
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.
Summary
A resource operation that borrows another resource's route with
routeNamenow resolves relation IRIs through the borrowing resource's operation and provider.Reproduction
A
CategoryProjectionborrowingCategoryResource's item route was emitted as/shared_iri/categories/1, then rejected as an invalid IRI when posted to aCategoryProjectionrelation.Test plan
Fixes #8503