ChilliCream / ChilliCream/graphql-platform
Allow overriding query convention result name per field
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5.8k
- Forks
- 810
- Avg merge
- 15h 39m
- Merged PRs (30d)
- 98
Description
Product
Hot Chocolate
Is your feature request related to a problem?
Currently, HotChocolate names the query convention result types by the field.
I have several fields in different parts of the hierarchy with the same name, and I need to use query conventions for both.
The solution you'd like
The ability to override the query convention result type name per field using an attribute, just like overriding the result type name for mutation conventions or the connection name for pagination.
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
Review the query conventions implementation and compare it with the existing mutation-convention result-name and pagination connection-name overrides. Define the per-field attribute behavior so fields with the same name can produce distinct query convention result types, then add coverage demonstrating both an override and the default naming behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100