You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we have several instances in our codebase where key={index} is used when rendering lists with the .map() function. While using the index as a key works, it can lead to performance issues and bugs when the list changes. Using a unique identifier as the key is recommended to ensure that React can efficiently track which items have changed, added, or removed.
Proposed Solution
Replace index with unique keys.
Screenshots / Mockups
If applicable, add images for mockup purposed
How will this move the needle on health equity?
Performance improvement for the site.
The text was updated successfully, but these errors were encountered:
Background
Currently, we have several instances in our codebase where
key={index}
is used when rendering lists with the .map() function. While using the index as a key works, it can lead to performance issues and bugs when the list changes. Using a unique identifier as the key is recommended to ensure that React can efficiently track which items have changed, added, or removed.Proposed Solution
Replace
index
with unique keys.Screenshots / Mockups
If applicable, add images for mockup purposed
How will this move the needle on health equity?
Performance improvement for the site.
The text was updated successfully, but these errors were encountered: