Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit b814697

Browse files
committed
Merge pull request facebook#2209 from glenjamin/patch-2
[docs] Clarify wording on sub-tree reconciliation
1 parent d15620a commit b814697

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/docs/ref-08-reconciliation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,7 @@ In practice, finding a key is not really hard. Most of the time, the element you
122122

123123
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.
124124

125-
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.
125+
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.
126126

127127
Because we rely on two heuristics, if the assumptions behind them are not met, performance will suffer.
128128

0 commit comments

Comments
 (0)