ChilliCream / ChilliCream/graphql-platform
Change naming for generated classes
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5.8k
- Forks
- 810
- Avg merge
- 15h 39m
- Merged PRs (30d)
- 98
Description
Product
Strawberry Shake
Is your feature request related to a problem?
Im trying to map this query to my c# code:
this is my graphql file:
and this is my generated code:
The solution you'd like
either awoid the reserved names automaticcly or allow overriding classes name during generation
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the GraphQL file and generated C# shown in the issue to identify which names conflict with C# reserved names. Then trace the Strawberry Shake generation path that produces those classes and determine whether automatic renaming or user-defined class names is the intended behavior. Done means generated classes can be mapped without reserved-name conflicts, with coverage for the chosen behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100