Outdated scheduling in "Design Principles"
還沒有人認領這個 Issue。
- 主要語言
- JavaScript
- 星號
- 11.8k
- 分支
- 7.9k
- 平均合併
- 1 天 11 小時
- 30 天內合併 PR
- 11
描述
This is a subtle distinction but a powerful one. Since you don’t call that component function but let React call it, it means React has the power to delay calling it if necessary. In its current implementation React walks the tree recursively and calls render functions of the whole updated tree during a single tick. However in the future it might start delaying some updates to avoid dropping frames.
If something is offscreen, we can delay any logic related to it. ... To be clear, we are not taking advantage of this right now.
As far as I understand, React is taking advantage of delaying updates? https://github.com/facebook/react/issues/6170#issuecomment-318204454
If that's the case, seems like this part of the docs is outdated.
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
找到「Design Principles」文件頁面,並結合連結的 React issue 和留言,檢視引用的排程相關段落。確認這些陳述是否已經過時,然後修改受影響的措辭,使其符合 React 目前的更新排程行為,並驗證文件變更。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- javascript, react
- 領域
- documentation
- Issue 類型
- 文件
- 難度
- 2/5
- 預估耗時
- 1-3 小時
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 38/100