fix: Reading associations via the parent, if the parent has multiple associations of the same type and to the same entity (backport: 6.6.x)#15206
Merged
Michael Telgmann (mitelg) merged 2 commits into6.6.xfrom Feb 26, 2026
Conversation
|
4180355 to
e1fbe2e
Compare
Nicolas Fortier (nfortier-shopware)
approved these changes
Feb 26, 2026
…associations of the same type and to the same entity
e1fbe2e to
d527181
Compare
Jonas Elfering (keulinho)
approved these changes
Feb 26, 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.
Backport: #14215
1. Why is this change necessary?
Reading child associations via the parent entity is broken, if the parent has multiple associations of the same type to the same child entity.
e.g. the relation from the customer to its default shipping and billing address.
2. What does this change do, exactly?
Fix the
ApiControllerso it is not only checking if the reference definition is matching, but also the reference field.5. Checklist
RELEASE_INFO-6.<major>.mdunder “Upcoming” for informational changes, including the consequences of the change and how it affects external developers.UPGRADEsection inUPGRADE-6.<next-major>.mdfor breaking changes (what/why/impact/how to adapt).