Incorrect Schema When Using Mutation Conventions

[nollidnosnhoj]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When using mutation conventions and explicitly defining the type and field name for payload, it produces the incorrect schema.

According to the documentation, the PayloadFieldName is the name of the field in the payload that represents the data....

type Mutation {
  createUser(input: CreateUserCustomInput): CreateUserPayload
}

type CreateUserPayload {
   thisIsTheFieldName: User
   errors: [CreateUserError!]
}

... and PayloadTypeName is the type name of the payload.

type Mutation {
  createUser(input: CreateUserCustomInput): ThisIsTheTypeName
}

Here is the C# code.

[UseMutationConvention(
        InputArgumentName = "input", 
        InputTypeName = "HelloWorldInput", 
        PayloadFieldName = "message", 
        PayloadTypeName = "HelloWorldPayload"
)]
public string HelloWorldAsync(string name)
{
    return $"Hello, {name}!";
}

Expected schema:

type Mutation {
  helloWorldAsync(input: HelloWorldInput!): HelloWorldPayload!
}

input HelloWorldInput {
  name: String!
}

type HelloWorldPayload {
  message: String
}

Actual schema:

type Mutation {
  helloWorldAsync(input: HelloWorldInput!): message!
}

input HelloWorldInput {
  name: String!
}

type message {
  HelloWorldPayload: String
}

In the actual schema, the field and type name are switched.

One thing to note, I've tried this without explicitly defining type and field names (no arguments in mutation convention attribute), and the schema got the payload type correct (based on convention), but the payload field name is string, (which I assume is working as intended since I am only returning a string, not an object.)

Please let me know if I need more information. I am happy to provide more! And lastly, I am new to GraphQL so I may be getting things wrong. If so, let me know!

Thanks!

Steps to reproduce

1. Create a mutation that uses the mutation convention.
2. Ensure that the mutation method returns a string, or any type that isn't an object.
3. In the convention, explicitly define the Payload field and type name.

Relevant log output

No response

Additional Context?

No response

Product

Hot Chocolate

Version

12.4.0

[PascalSenn]

@nollidnosnhoj Ooops, refactoring bug! Thanks for reporting!!