Strawberry Shake: Code generation fails when GraphQL field names conflict with System.Object method names

Product

Strawberry Shake

Version

15.1.11

Link to minimal reproduction

https://github.com/karlssberg/strawberry-shake-bug

Steps to reproduce

1. Create a GraphQL schema with a type containing a field named equals:

type StringMatch {
  equals: String
}

2. Generate Strawberry Shake client code
3. Attempt to build the project

What is expected?

The code generator should detect C# reserved method names and either:

• Automatically suffix the property name (e.g., Equals → EqualsValue or Equals_)
• Provide a configuration option to customize property naming
• Change source generation to use explicit interface implementations to avoid member name clashes

What is actually happening?

Generated code creates a property named Equals which conflicts with System.Object.Equals(object), causing compilation errors:

error CS0102: The type 'StringMatch' already contains a definition for 'Equals'

Additional context

Also affects input declarations that contain fields matching System.Object method names.

Start with the minimal reproduction linked in the issue and generate the client code for the StringMatch type and the affected input declaration. Inspect the generated members and the Strawberry Shake code-generation entry points that produce them. Done means the generated project builds when GraphQL fields match System.Object method names, without breaking ordinary field generation.