useAsyncCallback doesn't require a dependency array?

[theogravity]

I'm trying to use this in place of react's useCallback(), and was wondering if a dependency array is required as I don't see one in the signature. Based on the usage examples, I get a sense that this isn't meant to replace it?

[JoshWellPharma]

No this is not like reacts useCallback. Instead you use useAsyncCallback when you want to control when the async operation happens. E.g. on a form submit.

you could do something like:

// where createUser is your async function that creates you a user
const createUserAsync = useAsyncCallback(createUser);
const onSubmit = (values) => createUserAsync.execute(values);

<form onSubmit={onSubmit}>
<input name="email" />
<input name="password" type="password" />
</form>

[behnam-oneschema]

For anyone landing here, this seem to be the solution to make the useAsyncCallback usage dependency-aware:

const myAsyncCallback = useAsyncCallback(
  React.useCallback(
    async (foo: number) => {
      return foo + bar
    },
    [bar]
  ),
)

where React.useCallback does the "re-create function object upon dependency change" part of the problem, while useAsyncCallback does the state management and error catching.

I think it's a similar thing with the useAsync API, as well. Just put the useCallback() inside it to take care of generating the proper function, then maybe customize the useAsync options to get the behavior you need upon params change.

Those said, it means that there's no need for updating react-hooks/exhaustive-deps options, and it would actually be incorrect to tell react-hooks/exhaustive-deps that useAsyncCallback or useAsync take a list of dependencies similar to React's in-built hooks.