feature: read and use operation types from schema

[mcarleio]

Instead of using hardcoded values for the operation types Query, Mutation and Subscription, read type names from schema block inside the schema itself (see https://spec.graphql.org/June2018/#example-e2969) and use hardcoded values as fallback.

[berngp]

The Query, Mutation, and Subscription types are establish already as the base types for GraphQL operations by the spec.
I don't think it will be a good idea to allow folks to override it.

[mcarleio]

Hm, I agree, that Query etc are established as base types, but the GraphQL specification allows to change them and so should any compliant library do. Especially as it is not that much of an effort.
But for most people, sticking with Query etc is probably fine.

[berngp]

@srinivasankavitha what do you think?

[srinivasankavitha]

I think this is not a trivial effort since it requires the dgs-framework to also recognize the same. We have a few places in the framework that assume these types, and will need to make sure they all work together. Since it is not a very common use case, I'm in favor of deferring adding support for this till we have a clear need.

…

On Sun, Jul 10, 2022 at 11:54 PM Bernardo Gomez Palacio < ***@***.***> wrote: @srinivasankavitha <https://github.com/srinivasankavitha> what do you think? — Reply to this email directly, view it on GitHub <#327 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJ5JPXPLRHUOUBSZT4SL2QTVTPAKRANCNFSM5OFA6K7Q> . You are receiving this because you were mentioned.Message ID: ***@***.***>