Resetting state docs improvement
還沒有人認領這個 Issue。
- 主要語言
- JavaScript
- 星號
- 11.8k
- 分支
- 7.9k
- 平均合併
- 1 天 11 小時
- 30 天內合併 PR
- 11
描述
Over here: https://react.dev/learn/preserving-and-resetting-state#option-1-rendering-a-component-in-different-positions
about resetting a state, just because a line is drawn to the right, now the Counter becomes a "right" child?
And then, just because the line is drawn to the left, now the Counter becomes a "left" child?
The diagram is:
In reality, it is just "children" nodes. So if you have one child with a line drawn to the left, it doesn't make it a "left" child.
Likewise, if you have one child with a line drawn to the right, it doesn't make it a "right" child.
To some degree, it dumbs down the programmers.
The truth is:
For those three situations in the diagram:
- First child is
Counter, and second child isfalse. (isPlayerA && whateverbecomesfalseifisPlayeris false). There should be a solid line going to afalseas a second child. - First child is
false, and second child isCounter. There should be a solid line going down to the first child which isfalse. - The third case is just like (1).
And then, the rule of React is, the false will not be rendered. But the tree in fact has a false, for the "tree structure" to be "different".
If I am not mistaken, this "tree" is composed, and compared to the previous "tree", for React to decide whether to change something in the actual DOM. This "current" tree and "previous tree", is the idea of Virtual DOM.
So the concepts should be set straight here.
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
從連結的「Option 1: Rendering a component in different positions」區段開始,檢查其中關於條件式子元素的圖示和說明。將措辭與 React 處理 false children 以及樹狀結構中位置的方式進行比較。當圖示和文字準確解釋這三種情況,且沒有暗示視覺上的左側或右側位置定義子元素的 identity 時,即視為完成。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- javascript, react
- 領域
- documentation
- Issue 類型
- 文件
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100