Skip to content

Commit ae71605

Browse files
committed
revert update to usage of index as key wording
1 parent 6f0dfce commit ae71605

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/docs/reconciliation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,7 @@ In practice, finding a key is usually not hard. The element you are going to dis
138138

139139
When that's not the case, you can add a new ID property to your model or hash some parts of the content to generate a key. The key only has to be unique among its siblings, not globally unique.
140140

141-
As a last resort, you can pass item's index in the array as a key. This can work well if the items are never reordered. However, there will be a performance impact with reordering as React will naively update components.
141+
As a last resort, you can pass item's index in the array as a key. This can work well if the items are never reordered, but reorders will be slow.
142142

143143
There can also be issues with the state of a component in a list if indexes are used as keys. The state of an item in a list (or any deep state inside of it) will stay attached to the original position of the item, even if the item has “moved” in the data source. This is particularly noticeable with inputs retaining their values in the original positions even when their parent components reorder or are prepended to.
144144

0 commit comments

Comments
 (0)