Hooks side effects / callbacks?

[empz]

I've just started with the library and it feels like I can't have the best of bost worlds (declarative and imperative) with this library.

If I go with the direct call option, then I lose the "isExecuting" to show a loading state (I have to manage my own loading state). If I go with the hook option (useAction) I get all the nice isExecuting, isIdle, hasErrored, hasSuccedeed which is very convenient and familiar for anyone that had used React-Query. The thing is, if I want to react to an error imperatively there's no way to do that at the moment. I mean, checking the hasErrored and performing the action is not ideal, because the action might contain side effects and we would only want to trigger it once.

React Query solves this by allowing us to set callbacks when declaring the mutation (see https://tanstack.com/query/v4/docs/framework/react/guides/mutations#mutation-side-effects).

It would be great if this library would allow us to do something similar, something like:

const { execute, result, isExecuting } = useAction(someAction, {
  onSuccess: (result) => { console.log(result) },
  onError: (error) => { console.error(error) },
  onSettled: (result, error) => { console.log(result, error) }
})

Thoughts?

[empz]

Shame on me. I totally missed it. https://next-safe-action.dev/docs/execution/hooks/hook-callbacks