[Bug]:Possible wrong descrption for useDeferredValue
還沒有人認領這個 Issue。
- 主要語言
- JavaScript
- 星號
- 11.8k
- 分支
- 7.9k
- 平均合併
- 1 天 11 小時
- 30 天內合併 PR
- 11
描述
Summary
The doucmention describe the wrong behaviour for useDeferredValue
Page
https://react.dev/reference/react/Suspense
Details
The documentation says:
The query will update immediately, so the input will display the new value. However, the deferredQuery will keep its previous value until the data has loaded
From my test, deferredQuery also updates immediately rather than waiting for the data to be loaded here is the link https://codesandbox.io/p/sandbox/react-dev-forked-kxfktt
useDeferredValue consistently lags query with around 4 or 5 ms
Think about it, if deferredQuery updates after SearchResults is ready, how SearchResults receive the latest data at the first place?
The real reason we can see opacity: 0.2 for several seconds is that the new content is not rendered yet; rather than
the deferredQuery will keep its previous value until the data has loaded
If my understanding is correct, I should say the documentation is misleading, especially for the newbies
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
閱讀 https://react.dev/reference/react/Suspense 上關於 useDeferredValue 的段落,並在連結的 CodeSandbox 中重現該行為。比較關於 deferredQuery 的措辭與觀察到的時序,然後更新文件,使其準確說明值何時變更,以及不透明度表示什麼。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- react
- 領域
- documentation
- Issue 類型
- 文件
- 難度
- 2/5
- 預估耗時
- 1-3 小時
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 52/100