SWRV returns wrong cached data before first fetch while using key watcher function.

CodeSandbox: https://codesandbox.io/s/swrv-first-fetch-key-ip6ox?file=/src/App.vue Click on the add button and see that check turns false.

I’d assume that the data returned by useSWRV is either undefined (no cache and data not yet available), or some cached data for that key (That is, check to be always true). Not some cached data for some older value of the key.

[ivos]

Better yet, we could have a new return value named isLoading that would be true when there’s a request ongoing and the data is either undefined or does not correspond to the current key.

That way users can show a spinner when either:

1. data is undefined, when showing cached data for the previous key is better than the spinner.
2. isLoading is true, when showing cached data for the previous key is undesirable.

[darrenjennings]

Is this because you’ve replaced using it with another library, found it wasn’t needed in practice, moved away from Vue or something else…? I am about to start using it (or something similar) to deduplicate requests, so would be great to hear why before I start.

Hello @pbowyer! I had a vested interest in this library when I was employed at Kong, which included battle testing new features and guiding the api. I have a different job now but otherwise have no qualms with this library and would use it again if I build any vue apps! Happy to continue maintaining it until a community member steps up to do it.