RTK Query: Do we have a manual fetch function that follows cache rules as auto-fetch do

[xiaoyangfeng]

I have check the refetch function and trigger function from useQuery and useLazyQuery.
Looks like refetch will send a request to server and trigger will use the cache or send a request based on preferCacheValue.
However, what I am looking for is a function which applies same fetch rules as auto-fetch but triggered manually. For example, if I set refetchOnMountOrArgChange: 30, and the second call is fired after 30 secs, it should send a request otherwise return the cache.

[markerikson]

@xiaoyangfeng I'm not sure I understand what you're asking for here. Can you give a more detailed example?

[xiaoyangfeng]

lol. ok

[zousandian]

What hinders your user from repeatedly hammering F5 from getting that result? Usually, when a user already sees data, but wants it refetched, I'd personally say honor that wish.

I have a similar need.
For example, when an <SearchInput/> has auto suggestion feature, just like Google, the search function is triggered by the onChange event. A user may edit their input, from Rect to React for example, which may trigger two times Re search.
We can cache the Re result for a moment to improve the speed. But after later, when the user search something like Reselect, which trigger Re search again, we still want to make a request to get new data.

[phryneas]

I would assume that if you query to "https://example.com/search?q=Re" you would expect the result to be the same every time? On which grounds would you expect a different result between the first time, the second time and the third time you call it?
From what I see the server has no additional data and will not be able to destinguish between three times the same request?

[zousandian]

d will not be able to destinguish between three times the same request?

When query something like /business/receipts/list?sn=202201..., may new data be generated from other place every few moment.

[phryneas]

So this is a time-related thing? In that case, why not just reduce the cache-lifetime if something is not on screen for that endpoint? keepUnusedDataFor​

[phryneas]

You can do that by doing

const request = dispatch(
    api.endpoints.myEndpoint.initiate(arg, {
        forceRefetch: 30,
    })
)
// make sure to call this before your component unmounts or the data will never be removed from the cache
request.unsubscribe()

[xiaoyangfeng]

Thanks, that works! Any plan to add this as a build in function to the result of useQuery and useLazyQuery?

[phryneas]

No, you are the first person to ever request such a functionality and it is pretty different from how the library is usually being used, so you'll have to stick to using it directly.