Delete cache entry

[YuriyDyachkov]

Hello!
Is there a way to remove cache entries with the same name without being bound by arguments? I need to remove them, and not invalidate them.

For example these:

I have 2 lists with items and inside each item it is possible to see items from the second list. That is why it is important that when I make manipulations in one list, the actual data (sorting, deleting, changing) is displayed inside the item from the second list. I hope this doesn't sound like a complicated explanation.
Cache invalidation is not working correctly because on list 1 page I can't update a specific entry from list 2 because I don't know its ID. And this provokes unnecessary queries to the database during some actions.

[markerikson]

Not directly, no. RTK Query is very based on the idea of passing in cache key arguments for the logic to know which cache entry you're dealing with.

Can you clarify what you mean by "remove, not invalidate"?

[YuriyDyachkov]

@markerikson, thanks for the quick response. I want to remove it from the store and not use tag invalidation.
Because invalidatesTags will make a repeated request to the database. I do not need it.

[EskiMojo14]

Invalidation will only make a request if you still have components subscribed to the data. If none of your components are using the data anymore, it'll be removed from store for you.

[YuriyDyachkov]

@EskiMojo14, I didn't quite understand you. My list item component is subscribed to cached data.
If I invalidate an item from the second list, when, for example, I change the sorting in the first list, then this causes a repeated request to the item from the second list, although it may already have been deleted.

[kaung-minkhant]

I would like to achieve this feature as well. In my use case, I was using in react-native with react navigation. The problem with react navigation is that, even though a screen is not shown on screen, that screen component does not unmount as it is part of the navigation life cycle. So, that component ends up still subscribed to the cached data. Even if we wish to reset navigation and delete cache data, if we use invalidation, the query in that screen gets refetched which I do not want. So the ideal behavior would be, to be able to delete the cache entries, remove all the related subscriptions. I would like to achieve it somehow.

[phryneas]

@kaung-minkhant if you were to delete the cache entry while it is still mounted in the background it would either need to refetch and go back to loading in the background or that background screen would crash. Deleting isn't the solution here.

[tylercaceres]

I would like to achieve this feature as well. In my use case, I was using in react-native with react navigation. The problem with react navigation is that, even though a screen is not shown on screen, that screen component does not unmount as it is part of the navigation life cycle. So, that component ends up still subscribed to the cached data. Even if we wish to reset navigation and delete cache data, if we use invalidation, the query in that screen gets refetched which I do not want. So the ideal behavior would be, to be able to delete the cache entries, remove all the related subscriptions. I would like to achieve it somehow.

In a similar situation currently, however for mine I have a screen, and within that screen is a component that makes a call. When I am unmounting my screen i call to invalidate tags, however the currently active "tag" (which is in a child component) does not get invalidated.