Skip to content
Discussion options

You must be logged in to vote

there isn't really any. It's just that if you use mutateAsync, you have to catch errors yourselves, or you'll get an unhandled promise rejection. Most of the time, having access to the actual promise is not necessary - unless you want to fire off multiple things concurrently. So you can just call .mutate and work with the callbacks.

if you look at how mutate is implemented - it's literally mutateAsync with a .catch(noop) attached and it doesn't return the promise, but keeps it to itself :)

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@cmacdonnacha
Comment options

Answer selected by cmacdonnacha
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants