"mutate" side effects

[julius-hoffman]

It would be very useful to be able to include onSuccess, onError, onSettled callbacks to "mutate" function from useMutation as additional callbacks. We could use API similar to tanstack query.

mutate(someData, {
  onSuccess: (data, vars, context) => {
    // do something
  },
  onError: (error, vars, context) => {
    // do something
  },
  onSettled: (data, error, vars, context) => {
    // do something
  },
})

[posva]

This was intentionally not added because you can just do mutateAsync().then(onSuccess).catch(onError).finally(onSettled). Any blocker to not use this syntax? It should be also easy to migrate with ast-grep

[julius-hoffman]

IMHO, it's just more declarative and easier to read, plus there's no immediate access to data, variables and context if we use then/catch/finally. Ofc we could use it from the returns of useMutation but again I think it comes down to how convenient it is.

[posva]

Is there any particular case that isn't doable with the syntax above?