Support multiple projects in graphql config

[Briaoeuidhtns]

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.

[Briaoeuidhtns]

I'm willing to look into it, but want to make sure I'm not missing something and that it's reasonable.

[michaelstaib]

We have this on our list. If you want to take this on you can. The part we have implemented of the graphql config is very small. So there is lots to do to get this working.