GraphiQL: "Error: Mutation fields must be an object with field names as keys or a function which returns such an object." about kgraphql HOT 3 CLOSED

Hi @TobiasWalle, thank you for your report!

I've played a little bit with GraphiQL and reproduced your issue. As you said, GraphiQL requires mutation object with at least one field. No mutation object in schema yields same error, and in my opinion this is a bug in GraphiQL.

GraphQL specification explicitly states that:

The mutation type is optional; if it is null, that means the system does not support mutations. If it is provided, it must be an object base type.

Moreover, it does not state that Object type has to contain at least one field.

Adding built-in mutation field (like in graphql-ruby library you've linked) is dirty workaround. Right now, I think we should create section on documentation about integration with Graphiql, and leave creating mutation fields to users.

from kgraphql.

Hello @pgutkowski, thank you for reviewing this issue.

I also want to thank you for the work you putting in this library. I really enjoy using it.

from kgraphql.

Thank you @TobiasWalle for your kind words! I hope you won't meet any further problems using KGraphQL in future.

from kgraphql.