mirror of
https://github.com/facebook/react.git
synced 2026-11-18 20:15:56 +00:00
[docs] Clarify wording on sub-tree reconciliation
The previous wording could be interpreted to mean sub-trees moving from within one sibling to within another, rather than the shuffling of siblings on a single level as intended
This commit is contained in:
1 parent
21f601964f
commit
cf512bf60d
1 file changed
+1
-1
@@ -122,7 +122,7 @@ In practice, finding a key is not really hard. Most of the time, the element you
|
||||
|
||||
It is important to remember that the reconciliation algorithm is an implementation detail. React could re-render the whole app on every action, the end-result would be the same. We are regularly refining the heuristics in order to make common use cases faster.
|
||||
|
||||
In the current implementation, you can express the fact that a sub-tree has been moved between siblings, but you cannot tell that it has moved somewhere else. The algorithm will re-render that full sub-tree.
|
||||
In the current implementation, you can express the fact that a sub-tree has been moved amongst its siblings, but you cannot tell that it has moved somewhere else. The algorithm will re-render that full sub-tree.
|
||||
|
||||
Because we rely on two heuristics, if the assumptions behind them are not met, performance will suffer.
|
||||
|
||||
|
||||
Reference in new issue
Block a user