Feature Request: option to refresh to not recursively refresh all upstream selectors · facebookexperimental/Recoil#1677

(6 留言) (1 反應) (0 負責人)JavaScript (19,428 star) (1,151 fork)batch import

enhancementhelp wanted

描述

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

貢獻者指南

技術棧: reactjavascripttypescript
領域: frontend
議題類型: feature
難度: 4
預計時間: 1-2 days
活動狀態: stale
清晰度: clear
前置要求: Recoil selectorsuseRecoilRefresher hookReact hooksCaching concepts
新手友善度: 35
研究方向: Examine Recoil's source code for the refresh mechanism, particularly the useRecoilRefresher hook and selector cache invalidation. Investigate how upstream selectors are recursively refreshed. Propose an API addition (e.g., a flag on the hook) to optionally disable recursive upstream refresh. Check the Recoil repository for any related discussions or prior attempts.