Skip to content
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

Open
hwillson opened this issue Jul 27, 2018 · 8 comments
Open

setting up multiple mutations #8

hwillson opened this issue Jul 27, 2018 · 8 comments
Labels
core Feature requests related to core functionality project-apollo-client (legacy) LEGACY TAG DO NOT USE

Comments

@hwillson
Copy link
Member

Migrated from: apollographql/apollo-client#3231

@misterbridge
Copy link

Any news on that ?

@martinlynge
Copy link

martinlynge commented Oct 19, 2018

@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 <Mutation /> component. When do you expect to publish this section?

@KevinHewson
Copy link

@hwillson - Just looking to see if you have published the updated docs with the new section about nested/multiple mutations with the <Mutation /> component. I looked but I don't see it yet.

@garfiaslopez
Copy link

Still waiting :c plz, help.

@AnselmMarie
Copy link

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.

constructor(props) { this.props.navigation.setParams({ thisScreen: this, }); }

@misterbridge
Copy link

@AnselmMarie sure but that's not using the Query and Mutation components.
Yes there are solutions to do multiple queries and mutations (things like react-adopt work also pretty well) but there's still nothing on the appolo's components themselves yet.

@AnselmMarie
Copy link

@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.

@miguelacio
Copy link

Still waiting for this, please be kind with us :c

@jerelmiller jerelmiller added the core Feature requests related to core functionality label Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Feature requests related to core functionality project-apollo-client (legacy) LEGACY TAG DO NOT USE
Projects
None yet
Development

No branches or pull requests

8 participants