Is this how useQueries should work ?

[craig-harbottle]

So, here's what I see is happening :

1. User clicks on a button to load some measurements. This is the log of useQueries results (and query key):

All good. Data is returned for each individual query and stored against the query key. The three loading states change to success.

2. User clicks to another measurement.

The initial response is 'success' and the data of the previous query is returned. But thereafter, the response for the measurement data the user clicked the btn for is returned.

Is this expected behaviour? If so, is there any way to prevent it? I want to be able to show a loader and to do that I need to be able to distinguish between 'success' and 'loading'. But that is complicated when the 'next' request returns some previous 'success' value.

My assumption would be that at step 2. (fetching new data), we should see a loading state and for the data to be reset to undefined (basically 1. again) . Thanks in advance :-)

[TkDodo]

how are you "loading measurements" when the user clicks a button? I think you would get your expected behaviour if you change the query-key whenever the user clicks the button, which will create a new cache entry, so it starts with undefined data and loading state again.

if you re-use the same query key (maybe by calling refetch(), I don't know...?), you will get the cached data and no isLoading state (though isFetching will be true). This is the desired behaviour because when refetching the same data (background refetch), it is usually not wanted to unmount the data and show a spinner instead. This is what stale-while-revalidate is all about :)

[craig-harbottle]

Hi @TkDodo - thanks for replying :-)

how are you "loading measurements" when the user clicks a button? - list item in an accordion

I think you would get your expected behaviour if you change the query-key whenever the user clicks the button, which will create a new cache entry, so it starts with undefined data and loading state again. - me too 🤔

Here're a at typical query key array. The measurementName changes on each btn click :

But that's not the correct data for that measurement. It's from the prev query.

• refetch() isn't called, afaik

[TkDodo]

can you create a codesandbox reproduction please? I can take a better look at a running example :)

[craig-harbottle]

Hi @TkDodo - my issue was fixed with a package update. The issue was prob this one. Thanks for taking the time to reply.