[GraphQL] Use correct resource configuration for filter args of nested collection#2976
Merged
alanpoulain merged 1 commit intoapi-platform:2.4from Aug 9, 2019
Merged
Conversation
Contributor
|
Should it be backported? It's a bug, but users may have come to rely on the buggy behaviour, no? |
Member
Author
|
I don't think so. The schema was generated with the wrong filters and you couldn't use them. |
teohhanhui
reviewed
Aug 9, 2019
alanpoulain
force-pushed
the
graphql-fix-nested-filters
branch
from
b685c72 to
92723fb
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
2 participants
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 of #2970