Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GraphQL] Introducing @cascade in the GraphQL API? #4789

Closed
hackintoshrao opened this issue Feb 17, 2020 · 0 comments · Fixed by #5511
Closed

[GraphQL] Introducing @cascade in the GraphQL API? #4789

hackintoshrao opened this issue Feb 17, 2020 · 0 comments · Fixed by #5511
Labels
area/graphql Issues related to GraphQL support on Dgraph. kind/enhancement Something could be better. status/needs-attention This issue needs more eyes on it, more investigation might be required before accepting/rejecting it

Comments

@hackintoshrao
Copy link
Contributor

hackintoshrao commented Feb 17, 2020

What you wanted to do

This is briefed in https://discuss.dgraph.io/t/graphql-nested-filter/5997

What you actually did

Try to filter based on a deeper feature in the GraphQL query.

Why that wasn't great, with examples

I need to write custom logic with GraphQL+- to achieve this, the link here, discussed the issue in detail.

Any external references to support your case

https://discuss.dgraph.io/t/graphql-nested-filter/5997

@MichaelJCompton MichaelJCompton added the area/graphql Issues related to GraphQL support on Dgraph. label Feb 24, 2020
@MichelDiz MichelDiz added status/needs-attention This issue needs more eyes on it, more investigation might be required before accepting/rejecting it kind/enhancement Something could be better. labels Feb 25, 2020
abhimanyusinghgaur added a commit that referenced this issue May 27, 2020
dna2github pushed a commit to dna2fork/dgraph that referenced this issue Jul 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/graphql Issues related to GraphQL support on Dgraph. kind/enhancement Something could be better. status/needs-attention This issue needs more eyes on it, more investigation might be required before accepting/rejecting it
Development

Successfully merging a pull request may close this issue.

3 participants