Asynchronous mutations are handled when finished.

[mhverbakel]

Bug report

Description / Observed Behavior

When you provide an asynchronous function to the mutate function, the duration of the Promise does not seem to affect the other processes until it is resolved. isValidating is false for the duration of the Promise, and the automatic refresh intervals still get executed during the remote update.

Expected Behavior

When mutate is called with a data function that returns a Promise, the isValidating should go to true immediately, blocking any scheduled refreshing of the data.

Repro Steps / Code Example

https://codesandbox.io/p/sandbox/ts8qx3 (instructions included in example)

Additional Context

SWR Version 2.2.5

The test suite has tests for local mutations which includes tests for isValidating, but the remote mutation tests seem to lack this.

[Oripi]

tried to dig into the code, but i guess it's more than a 15m job :)
looks like the mutation is awaiting for the data without updating the state of the swr hook.
the awaiting code: https://github.com/vercel/swr/blob/main/src/_internal/utils/mutate.ts#L165
hopefully a maintainer will notice this and try to solve it :)