Just want to place my vote to for this to be prioritised. The issue I have is that because there are no validations in DQL, then it creates a situation where DQL mutations in my codebase can easily become outdated as the schema evolves—which could lead to a situation where an outdated DQL mutation is running in production creating bad data, which leads to broken graphql queries because endpoints start returning non nullable field errors:
"Non-nullable field 'platform' (type String!) was not present in result from Dgraph. GraphQL error propagation triggered.
Which of course is not a situation you can resolve with a couple of clicks.
Until DQL has validations, or transactions are possible in graphql I’m gonna feel nervous every time I modify the schema.