fix(metadata): nested property filters fail to generate JOINs when relation target entity is not directly declared as ApiResource#7926
Open
Maxcastel wants to merge 4 commits intoapi-platform:4.3from
Conversation
Maxcastel
force-pushed
the
fix-nested-property-join-relation-not-ApiResource
branch
6 times, most recently
from
3b12c66 to
d886a12
Compare
…Trait::getClassNameFromProperty()` api-platform#7916
Maxcastel
force-pushed
the
fix-nested-property-join-relation-not-ApiResource
branch
from
d886a12 to
9473d96
Compare
Maxcastel
force-pushed
the
fix-nested-property-join-relation-not-ApiResource
branch
7 times, most recently
from
d65a42f to
4009120
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.
Uh oh!
There was an error while loading. Please reload this page.