Calling a mutation with a secondary client about apollo-link-state

[jbaxleyiii]

➤ stale[bot] commented:

This issue has been automatically labled because it has not had recent activity. If you have not received a response from anyone, please mention the repository maintainer (most likely @jbaxleyiii). It will be closed if no further activity occurs. Thank you for your contributions to React Apollo!

[jbaxleyiii]

➤ Bryan Young commented:

I ended up working around this by making a manual client call and passing the data to the child component manually. I still maintain it’s a bug, and would love to help however I can. @jbaxleyiii

[chadacious]

I've also encountered this problem specifying the client in the graphql options at the same line of code as mentioned by jbaxleyii. Seems that it should be wrapped in something like: if (this.type === DocumentType.Query) {...}
I guess I'll have to do the same workaround for now. I agree its a bug.

[benoitgrelard]

I am also encountering the issue, same conditions:

• mutation
• using a secondary client provided via options

[DanMannMann]

I'm encountering the same issue, but in a component which composes a query and 2 mutations all using a secondary client. Everything works fine the first time the component is rendered if I compose in the order mutation1,mutation2,query (i.e. query last). Any action which subsequently causes the component to be re-rendered will result in the following:

The operation 'myMutation' wrapping 'Apollo(Apollo(MyComponent))' is expecting a variable: 'myVariable' but it was not found in the props passed to 'Apollo(Apollo(Apollo(MyComponent)))'

If I compose as query,mutation1,mutation2 (i.e. query first) then it also fails on the first render with the same error.