Can not mutate data from SWRInfinite with `revalidateFirstPage: false` when key is not mounted

Bug report

I can not manually refresh data using mutate when using SWRInfinite and revalidateFirstPage: false and key of that mutate is not bound to current page.

Description / Observed Behavior

I have a list of items, which I fetch using useSWRInfinite. Since I do not want to fetch the first page everytime user fetches next page, I use it with revalidateFirstPage: false option, and that works great. So, imagine I have a list of items: A, B, C, D, E. Each item have also its own details page. I can change item A to Aa and use mutate when I am on list page to refresh cache without calling request again, and that also works. The problem is when I go to page A and change that item’s name to Aa - even though I call exactly the same methods, when I go back to list page, the item is still A, not Aa. I tested it a lot of times, and that scenario works when I remove revalidateFirstPage: false from useSWRInfinite. But without it I have to load first page every time user scrolls down, which slows down loading new data…

Expected Behavior

Cache is always updated when using mutate, but first page is not fetched everytime when I want to fetch n+1 page

Additional Context

SWR version 1.2.0

[tomaszczura]

@condinoaljoseph we migrated to react-query

[condinoaljoseph]

We can not use mutate returned from useSWRInfinite, since we need a way to mutate our cache from different components in our code, even those which do not use useSWRInfinite. Also, we can not use unstable_serialize, because we may not know the exact key - our real keys contain a lot of query params, and we want to modify all keys which contains some text (e.g. all with param type=image). We checked the cache, and key starting with $inf.... is always updated with our method, but this state is overwritten when going from point 3 to 4 (without any mutate or API call). What we discover is that if I have keyA for useSWRInfinite, you create two entries incache: one with keyA and one with $inf$keyA. Our useMatchMutate updates the second one, but does not touch the first. This approach worked in version 1.0.0-beta.5 (and earlier), and it still works when revalidateFirstPage is true.

If that is not a valid way of updating cache, do you have any adice for us how to update cache, when we do not know the exact key and without access to bound mutate?

we have same use case on our end, any updates?