Multiple Apollo mutations

Question

I followed the Apollo documentation to provide two mutations (createUser then signInUser) on a single React component, but one mutation (the "outer" one - signInUser) is not accessible to my code (this.props.signInUser is not a function). Maybe my server-side-enabled setup is masking one mutation, but I don't see where. Help appreciated :)

See full code here.

EDIT: same issue when using compose, see code.

score 3 · Answer 1 · 2016-11-09T12:29:01.107

3

You just need to name the mutations when passing them into the component, otherwise they are ALL called mutate, and override one another.

(By using the props function)

Here's a full example with named mutations:

https://gist.github.com/Siyfion/a2e9626ed431f8ff91af2c9b8cba1d67

edited Nov 09 '16 at 12:29

answered Nov 09 '16 at 11:44

Thanks but I have already renamed the mutations as instructed in the docs: `{ name: 'createUser' }` and `{ name: 'signInUser' }`. And when not providing such a name I believe the default is `mutate`, not `mutation`. Do you have a link to the Apollo documentation about this `props`? – Sébastien Dubois Nov 09 '16 at 11:56
Take a look at the second half of: http://dev.apollodata.com/react/mutations.html#calling-mutations – Nov 09 '16 at 12:28
Thanks, I tried to use `props` but same issue. I still suspect it's something in my server-side rendering setup (my `apollo` higher-order component). – Sébastien Dubois Nov 09 '16 at 12:52

score 0 · Accepted Answer · answered Nov 09 '16 at 13:00

It was caused by my apollo higher-order component which did more complex things than just calling Apollo's graphql (related to server-side rendering) and somehow must be masking properties. I bypassed this SSR behaviour for these mutations (not needed), see code.

Multiple Apollo mutations

2 Answers2