No input field null validation on non nullable fields

[MichelDiz]

@jdgamble555

According to graphql specs, a query should trigger an error if a null value exists on a field with !. We know dgraph does not do this, as we use @cascade to get around it. This is a separate issue, but needs to be looked at.

Pay attention that a Query and a Mutation are totally different things. So both have their own specs. In Dgraph we have this distinction too, only Upsert Block you can do some tricks outside of it. But in a mutation, you can only use RDF or JSON, never a DQL(like cascade directive) functions.

@jdgamble555

We know it does, however, throw an error when passing an argument to a variable with !, which works as expected.

In my view, that’s true via parameters/arguments in a query(or query inputs). I never saw a validation at the mutation level. Maybe someone could get an Apollo Server up and running to check if it does. As the docs aren’t helping much.

@jdgamble555

Like I said before, this still could be fixed with the right @auth directive (once you guys look at the field validation needs you can solve with very little coding by adding update-after).

I’ll ping some one about this. Does it has a ticket? I think you have some open tickets right?

@jdgamble555

We need to be able to implement the @nonNull directive in Dgraph Cloud, which would be on the Dgraph Team to do.

So, if GraphQL spec doesn’t cover it. We could potentially transpose the code(from graphql-non-null-directive) or do something similar in go and introduce it into the Dgraph core. So the directive would be native.

ping @mrjn @dmai @hardik