Document client prop

[estaub]

Support for the client option on old-school graphql() queries is absent from <Query>.

graphql() options
<Query> options

This may have happened because the client option was never documented.

The original author of the client option PR was silent for 6 months, then posted this, indicating that he's no longer interested in working on it.

If the client option is deprecated, it would probably be good to post something, including a comment on the PR above so that subscribers see it, and a recommended approach to addressing a requirement for multiple clients.

The best way forward may be influenced by the functionality provided by the QueryRecyclerProvider in <ApolloProvider>; I'm afraid I don't understand what it does.

(Thanks!)

[astorije]

That would be great! We currently have a use case where we need to talk to more than one client, so that would make things cleaner.

[peaonunes]

The following code line from current version (2.1.9) and both Query and Mutation gives precedence to props client. So we can indeed override the default client via props.

// https://github.com/apollographql/react-apollo/blob/master/src/Query.tsx#L167
// https://github.com/apollographql/react-apollo/blob/master/src/Mutation.tsx#L120
...
this.client = props.client || context.client;
...

You would use like:

<Query query={query} client={client}>
...
</Query>

The feature is not documented though.
In addition to that the most common approach would be having a Gateway API running GraphQL and managing queries to different targets APIs. I wrote this article discussing some approaches if you really want to do that and pointing out some pros and cons.

[rosskevin]

Please PR any docs you would like to see. Client prop is definitely not going away.

[danilobuerger]

Documented here: https://www.apollographql.com/docs/react/api/react-apollo.html#query-render-prop