graphql/graphql-relay-js

Should mutation payload be non-null?

leethree opened this issue · 1 comments

Currently the mutation payload types are nullable. But it's not possible to be null because clientMutationId needs to be in the payload. So should we define the payload as non-nullable?

It should be nullable to allow error propagatee to mutation field and destroy the entire response.