Prevent inactive state

[loncar]

Is there a way of preventing inactive state for Query? I have noticed that only observable queries are non inactive. But if I create Query via queryCache.fetchQuery I don't have any observers on it and it is inactive right away even if I put staleTime and cacheTime to infinite.

Use case that I have is: getting some complex data by fetching across multiple endpoints with multiple requests per endpoint. Logic behind that is in Service part of App that is only at the end of processing used in React Component. But data will be there always and be invalidated by hand.

So question would be is there a easy way of using QueryCache fetching without Hooks and have caching layer with data being active (no inactive state)?

Thanks :)

[TkDodo]

So why would you need it to be in active state? As you said, only queries that have observers (rendered components via useQuery etc) are active. A query that is inactive will be garbage-collected after the cacheTime is reached - defaults to 5 minutes. If I got this right and you are only fetching, but never rendering, you can just increase the cacheTime and you data will be available via queryCache.getQueryData.

[TkDodo]

@sathish-karunakaran

1. a screenshot is not a codesandbox reproduction!
2. all I see is that you have a query that listens to the key for get-porfolio-asset-scores with an id that probably changes over time, going from 4 to 5 and then 55. As you likely only have have one useQuery call that looks something like this:

useQuery({
  queryKey: ['portfolio-service/get-portfolio-asset-scores', id, "AAPL US"],
  queryFn,
})

the output is totally expected, as only one id is active at the same time. This is the most I can tell from just a screenshot

[sathish-karunakaran]

Hi @TkDodo

Thanks for the reply

1. Try to reproduction on codesandbox with different API. since its not available for public
2. Yes I am using same usequery and changing the id field based on the user navigation.

navigating from 4 to 5 -> 5 will be stale and 4 will be inactive
Again I will navigating from 5 to 4 -> it needs to taken from the cache data but instead its fetching from service.

[TkDodo]

navigating from 4 to 5 -> 5 will be stale and 4 will be inactive

that is expected.

Again I will navigating from 5 to 4 -> it needs to taken from the cache data but instead its fetching from service.

with the default staleTime of zero, it will give you data from the cache immediately AND do a background refetch at the same time. If you don't want that, set a higher staleTime.

[bombillazo]

with the default staleTime of zero, it will give you data from the cache immediately AND do a background refetch at the same time. If you don't want that, set a higher staleTime.

Is there a way to not background refetch and use the same cache data until the staleTime has elapsed?

[TkDodo]

Is there a way to not background refetch and use the same cache data until the staleTime has elapsed?

That's exactly what staleTime does so not sure I understand the question...