mutation addUser($user: AddUserInput!) { addUser(input: [$user]) { user { ...UserSummary } } } I have a problem using input types as mutation parameters. The query and parameters are parsed and accepted by engine but query returns null. input AddUserInput { about: String …

Problem with input types in mutations

Leave_Trails (Leave Trails) July 20, 2022, 8:42pm 9

I think I had a problem with @auth directive
I noticed @auth directive on top of Language type
@auth(
add: { rule: “{$USER: { eq: “my_email@gmail.com” } }”}
)
Which prevented adding new record to Language

Topic		Replies	Views
Input fields set to null cause Internal Server Error GraphQL status:accepted , kind:bug , ticket:created	4	778	October 14, 2020
Mutation using dgo succeed but no displayed when I query it Dgraph Cloud kind:question	11	646	December 1, 2020
No input field null validation on non nullable fields GraphQL status:accepted , kind:bug , ticket:created	30	4509	March 22, 2022
Mutation to add object inserts null values -- with pydgraph Dgraph mutation , graphql	6	1170	May 13, 2020
Mutation failed because Dgraph execution failed because Some variables are used but not defined Dgraph Cloud kind:bug	3	724	February 23, 2021

Problem with input types in mutations

Related Topics