amirho/react.dev
1
0
Fork 0
mirror of https://github.com/reactjs/react.dev.git synced 2026-02-24 04:33:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

Split last sentence into its own paragraph

Browse Source
This commit is contained in:
Brian Vaughn
2017-11-29 14:05:05 -08:00
committed by GitHub
parent 97d4949954
commit 157501a48c
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/docs/lists-and-keys.md
View File

@@ -130,7 +130,9 @@ const todoItems = todos.map((todo, index) =>
);
```
We don't recommend using indexes for keys if the order of items may change. This can negatively impact performance and may cause issues with component state. (Check out Robin Pokorny's article for an [in-depth explanation on the negative impacts of using an index as a key](https://medium.com/@robinpokorny/index-as-a-key-is-an-anti-pattern-e0349aece318).) If you choose not to assign an explicit key to list items then React will default to using indexes as keys. You may read an [in-depth explanation about why keys are necessary](/docs/reconciliation.html#recursing-on-children) if you're interested in more information.
We don't recommend using indexes for keys if the order of items may change. This can negatively impact performance and may cause issues with component state. Check out Robin Pokorny's article for an [in-depth explanation on the negative impacts of using an index as a key](https://medium.com/@robinpokorny/index-as-a-key-is-an-anti-pattern-e0349aece318). If you choose not to assign an explicit key to list items then React will default to using indexes as keys.
Here is an [in-depth explanation about why keys are necessary](/docs/reconciliation.html#recursing-on-children) if you're interested in learning more.
### Extracting Components with Keys