Prevent data from being undefined when re-fetching

[paulintrognon]

Hi all, I want data to stick to its old value when re-fetching, instead of going back to be undefined. I could not find a param to get this behavior. Did I miss something obvious or is it just not an available feature?

Here's what I'd like:

1. first fetch happening, data === undefined
2. first fetch completed, data === [1, 2, 3]
3. second fetch happening, data === [1, 2, 3] (instead of undefined)
4. second fetch completed, data === [4, 5, 6]

Thanks all!

[gg2001]

Has anyone find a workaround to allow for this? Can't believe that this isn't documented anywhere, seems like a necessary feature.

[iamyoki]

I met that problem too, it's really frustrating, I haven't found any solution yet.

[ramyareye]

You might be wrong. useSWR by default caches the value until a new mutation.