-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setting up multiple mutations #8
Comments
Any news on that ? |
@hwillson in apollographql/apollo-client#3231 (comment) you mention that you are going to update the docs with a new section about nested/multiple mutations with the |
@hwillson - Just looking to see if you have published the updated docs with the new section about nested/multiple mutations with the |
Still waiting :c plz, help. |
About a month ago I ran across some documentation that might help out. I started to use the compose function and it allows you to use multiple queries and mutations without the nasty nesting. Go to this link for the documentation -> https://www.apollographql.com/docs/react/api/react-apollo.html#compose. After you check the compose section go to the graphql section, https://www.apollographql.com/docs/react/api/react-apollo.html#graphql, and start reading here to the bottom of the page. One disadvantage when using the compose function is not having access to the state or any functions in the class. I get around this by setting a new parameter in the react navigation to store the class.
|
@AnselmMarie sure but that's not using the Query and Mutation components. |
@misterbridge yeah but I wanted to comment an option just in case. I tried react-adopt but it didn't work from me. Every time I typed something in a text field it would focus out, pedronauck/react-adopt#29. I think the compose option is way better option than having nested components. |
Still waiting for this, please be kind with us :c |
Migrated from: apollographql/apollo-client#3231
The text was updated successfully, but these errors were encountered: