facebookexperimental/Recoil

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

Open

#1,677 opened on 2022年3月17日

GitHub で見る
 (6 comments) (1 reaction) (0 assignees)JavaScript (19,428 stars) (1,151 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
4
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Recoil selectorsuseRecoilRefresher hookReact hooksCaching concepts
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
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.