ChilliCream / ChilliCream/graphql-platform
Rename the root Query, Mutation, and Subscription elements
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?
I'm trying to use Fusion to merge an external graph (run by Hasura) that defines root elements as query_root, mutation_root, etc.
Fusion cannot merge the definitions of the graphs because the root elements in Hasura and Hot Chocolate are not the same. The Hasura graphs can't be changed (existing deployments), so I wanted to change the Hot Chocolate graphs to use the Hasura root element names.
I have tried everything and cannot get the exported schema to use query_root, mutation_root, etc.
The solution you'd like
I should be able to do something like [QueryObject(Name="query_root")] and have that reflected in the schema.
If that's not possible, maybe a way for Fusion to be able to rename root elements for external graphs?
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
The issue names no files, tests, or entry points to inspect. Start by locating the Hot Chocolate schema-generation code for root Query, Mutation, and Subscription types; done means an agreed mechanism lets exported schemas use names such as query_root, mutation_root, and subscription_root for Fusion compatibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100