ChilliCream / ChilliCream/graphql-platform
Support multiple projects in graphql config
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?
I have multiple graphql services I want to connect to, and I want to be able to generate independent clients for them. Other graphql tools (the lsp in particular) expect the graphql config to be at the root of the repo.
The solution you'd like
I want to be able to use the "projects" key in the config file to specify the graphql settings for each client. I'd expect the CLI would add a new option to select the project that would be required if it was ambiguous.
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 with Strawberry Shake's CLI handling of the root graphql config and its client-generation entry point. Trace how one configuration is selected, then assess support for the projects key and project selection when the config is ambiguous. Done means independent clients can be generated for multiple services from one root config.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100