[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