-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Dgraph do not accept valid GraphQL with inverse @dgraph directive #5744
Labels
Comments
pawanrawal
added
area/graphql
Issues related to GraphQL support on Dgraph.
kind/bug
Something is broken.
labels
Jun 26, 2020
pawanrawal
added a commit
that referenced
this issue
Jul 13, 2020
… with interfaces (#5911) Fixes #5744 There was another bug where field which map to reverse edges in Dgraph where generated as part of AddTypeInput and TypeRef. They have been excluded now as we can't perform a mutation along them. They would earlier have given an error at runtime while doing mutations in Dgraph about predicate being incorrect because it starts with ~. Apart, from that to fix #5744, we also allow interfaces implemented by the current type in the che
pawanrawal
added a commit
that referenced
this issue
Jul 14, 2020
… with interfaces (#5911) Fixes #5744 There was another bug where field which map to reverse edges in Dgraph where generated as part of AddTypeInput and TypeRef. They have been excluded now as we can't perform a mutation along them. They would earlier have given an error at runtime while doing mutations in Dgraph about predicate being incorrect because it starts with ~. Apart, from that to fix #5744, we also allow interfaces implemented by the current type in the che (cherry picked from commit ecec071)
parasssh
pushed a commit
that referenced
this issue
Jul 14, 2020
… with interfaces (#5911) (#5982) Fixes #5744 There was another bug where field which map to reverse edges in Dgraph where generated as part of AddTypeInput and TypeRef. They have been excluded now as we can't perform a mutation along them. They would earlier have given an error at runtime while doing mutations in Dgraph about predicate being incorrect because it starts with ~. Apart, from that to fix #5744, we also allow interfaces implemented by the current type in the che (cherry picked from commit ecec071)
dna2github
pushed a commit
to dna2fork/dgraph
that referenced
this issue
Jul 18, 2020
… with interfaces (hypermodeinc#5911) Fixes hypermodeinc#5744 There was another bug where field which map to reverse edges in Dgraph where generated as part of AddTypeInput and TypeRef. They have been excluded now as we can't perform a mutation along them. They would earlier have given an error at runtime while doing mutations in Dgraph about predicate being incorrect because it starts with ~. Apart, from that to fix hypermodeinc#5744, we also allow interfaces implemented by the current type in the che
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What version of Dgraph are you using?
Master
Have you tried reproducing the issue with the latest release?
v20.07
What is the hardware spec (RAM, OS)?
Steps to reproduce the issue (command/config used to run Dgraph).
Add this predicate to dgraph Schema
then try to push the following GraphQL Schema
Expected behaviour and actual result.
The schema should be valid and accepted by dgraph
but dgraph refuses the schema with the following error:
The text was updated successfully, but these errors were encountered: