Repository navigation
fix(doctrine): put-create under a slug parent link - #8688
Merged
soyuka merged 3 commits intoOct 16, 2026
Merged
Conversation
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.
A PUT that creates a resource under a parent link whose identifier is not the Doctrine id (e.g. a
nameslug) crashed withCannot assign string to property Company::$id of type ?int:PersistProcessorpassed the slug togetReference(), which only takes Doctrine identifiers.When the link identifiers match the Doctrine identifier fields we keep
getReference(), otherwise we look the parent up withfindOneBy()on the link identifiers (same rule as #8295).If no parent matches, the relation is left
null, same as before for a missing id: this does not add a 404 for an unknown parent.