Generated objects are incorrect for mutations and queries with the same name, as well as for subscriptions about dgs-codegen HOT 2 CLOSED

We don't support generation of types for subscriptions, we will create an issue for that.

For this example:

type Query {
    test(input1: String): String
    test(input2: String, input3: String): String
}

you can't have the same query name, it's not spec compliant, and graphql-java also throws an error.

For the case where you have the same name for a query type and a mutation type, in theory, it should work, although it is quite rare in practice to have the same operation name as an API for both a query and mutation. We could certainly handle it as you proposed, although it would be better practice to have better names that describe the operation in the schema.

from dgs-codegen.

I created a new issue for adding support for subscriptions as you suggested - #76
Closing this issue for now as it is a very rare scenario that you will have the same name for the query and mutation in your schema.

from dgs-codegen.