From 157501a48cdf9c4852eff89ae1fb408a2b562ab1 Mon Sep 17 00:00:00 2001 From: Brian Vaughn Date: Wed, 29 Nov 2017 14:05:05 -0800 Subject: [PATCH] Split last sentence into its own paragraph --- content/docs/lists-and-keys.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/docs/lists-and-keys.md b/content/docs/lists-and-keys.md index f9929921..a9c444a9 100644 --- a/content/docs/lists-and-keys.md +++ b/content/docs/lists-and-keys.md @@ -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