feat(multiple clients): add ability to define multiple clients

[samturrell]

Adds the ability to define multiple clients.

Builds on top of #12 with its runtime config functionality.

[Gomah]

Thanks @samturrell, I can't review it at the moment but will jump on it as soon as I can.

Also, as many people only use one endpoint, couldn't we just inject the default graphql client to the context as $graphql & use .default if we have more than one client?

e.g:

With one client:

const countries = await $graphql.request(countriesQuery, variables);

With multiple clients:

const countries = await $graphql.default.request(countriesQuery, variables);
const planets = await $graphql.planets.request(query);

[drewbaker]

Great idea to have the one client and multiple client approaches.

[samturrell]

@Gomah I thought about doing the same, but didn't want to make the API too confusing. Would also be a pain to upgrade in the future if users decide they need another endpoint, they would have to go through every request and update.

Happy to implement though if that's how you'd prefer it!

[samturrell]

@Gomah any updates on this?

[Gomah]

@Gomah any updates on this?

Hey @samturrell, sorry I was away. I will try to have a look in the next coming weeks

[Gomah]

Hey @samturrell,

Sorry for the delay, I just added a few comments before I can merge this one!

I'll make sure the docs are up to date with your changes & adjust the types

[samturrell]

@Gomah - I've amended in line with most of your comments. Let me know next steps whenever you can.

[Gomah]

Thanks @samturrell! Will merge this to develop & work on the docs + types before the release!