Augment filter argument for nested fields #208
Merged
Conversation
This file contains 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
This comment has been minimized.
This comment has been minimized.
If the field of GraphQL Type maps to an *..n relation (a list) and there is currently no `filter`-argument defined, we now generate it in the augmented schema. The logic for handling these nested filters is already implementd, so no further code-adjustments are required. resolves #129
Andy2003
force-pushed
the
bugfix/gh-129-augment-filter-argument-for-nested-fields
branch
from
e65c8e6 to
6e557a2
Compare
This comment has been minimized.
This comment has been minimized.
Andy2003
deleted the
bugfix/gh-129-augment-filter-argument-for-nested-fields
branch
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.
If the field of GraphQL Type maps to an *..n relation (a list) and there is currently no
filter-argument defined, we now generate it in the augmented schema.The logic for handling these nested filters is already implementd, so no further code-adjustments are required.
resolves #129