Data updated after isValidating becomes false

[RyKilleen]

Currently I'm experiencing some unexpected behavior.

I'm using useSWR with a custom fetcher. It returns isValidating as true, and then returns isValidating: false before the data is populated.

Is there any insight into why that might be? I know it's hard without code examples, I'll work to get a reproducible example. In short, would it be safe to assume that data should exist in the same life-cycle as isValidating becoming false?

I would expect the following order:

1. the call hasn't been made due to a tertiary.
2. That value changes, SWR sets isValidating to true, makes the call
3. The call resolves: SWR returns data and isValidating is set to false

Instead, number 3 is two steps.isValidating is false, and then step 4 is the data being populated.

[RyKilleen]

For anyone who stumbles upon a similar, unexpected behavior:

I was entering a state where the useSWR hook's revalidate() was being called in a useEffect, causing the anomaly above. Relocating the revalidate in a promise elsewhere alleviated the issue.