Feature Request: option to refresh to not recursively refresh all upstream selectors

from the docs https://recoiljs.org/docs/api-reference/core/useRecoilRefresher

It is currently a no-op to “refresh” an atom, it will retain its current state. Selectors will have their caches cleared. Because wrapper selectors are often used as abstractions, refreshing a selector will also recursively refresh the caches of all selectors that it depends on.

However, if those upstream selectors have not changed but is used from the refreshed selector it will once again refresh and refetch (if doing some data fetching). IMO a good solution is an option that we can pass in to refresh to not refresh upstream selectors especially since its also a common use case. the current behavior would cause a cascade of refreshes when a lot of them are unnecessary

[drarmstr]

Yes, we decided to start conservatively and invalidate all upstream selectors (including all upstream selectors for all possible values of dependencies). This default avoids missing refreshes if queries are performed from upstream selectors or secretly missing refreshes if wrapper selectors are added in abstraction layers, which is a common practice.

We discussed different options for minimizing the set of invalidations, but it hasn’t been a priority, so PRs are welcome. That’s because often when you want this much control over using Recoil as a local cache for remote mutable or changing data it can be better to use an atom with Atom Effects.

[drarmstr]

No work on this is currently planned, but we do accept PRs. In general I am personally wary of “refresh” and tend to recommend using atoms instead of selectors when users need more explicit control over updating values.