flat-fuchsia

mutation callback not running if the component unmounts

Why is this? Is this a technically limitation or a design choice? What is the rationale for this?

4 Replies

sunny-green•4y ago

it's in the docs: https://tanstack.com/query/v4/docs/guides/mutations#mutation-side-effects

Unlike queries, mutations are typically used to create/update/delete data or perform server side-effects. For this purpose, React Query exports a useMutation hook. Here's an example of a mutation that adds a new todo to the server:

sunny-green•4y ago

You might find that you want to trigger additional callbacks beyond the ones defined on useMutation when calling mutate. This can be used to trigger component-specific side effects. To do that, you can provide any of the same callback options to the mutate function after your mutation variable. Supported overrides include: onSuccess, onError and onSettled. Please keep in mind that those additional callbacks won't run if your component unmounts before the mutation finishes.

You might find that you want to trigger additional callbacks beyond the ones defined on useMutation when calling mutate. This can be used to trigger component-specific side effects. To do that, you can provide any of the same callback options to the mutate function after your mutation variable. Supported overrides include: onSuccess, onError and onSettled. Please keep in mind that those additional callbacks won't run if your component unmounts before the mutation finishes.

sunny-green•4y ago

oh and it's also here: https://tkdodo.eu/blog/mastering-mutations-in-react-query#some-callbacks-might-not-fire

Mastering Mutations in React Query

Learn all about the concept of performing side effects on the server with React Query.

flat-fuchsiaOP•4y ago

Ah yeah okay I can see that Haven't read the docs in a while we're still on v3 and I basically have most things memorized at this point

Gaming

Programming

mutation callback not running if the component unmounts

Did you find this page helpful?