qq, besides the UI(like GraphiQL, Insomnia, and so on) the usual clients throw errors based on the schema? Does it(the validation) work via cURL? is this validation a job for the client or the server? For me looks like a job for the client(Which Dgraph has none for GraphQL) that reads(introspects it) the schema. Right? How Dgraph would control the validation? There is a way to “deactivate” or “forgot to activate” the validation? Feels like something built-in the GraphQL itself, not the implementation code. See?
Something in my guts says that this is really odd. If this is part of the spec, and mandatory. Why Dgraph would be able to unnable it by mistake in the code? I can be wrong and the code has some flaws. But isn’t something missing somewhere? Are you guys using the Client the right way?
I will check this(this week) with different clients and ways to hit queries with other GraphQL solutions and compare the behavior.