Keys concept in React - Step-by-Step Execution

Concept Flow - Keys concept

Render list component

↓

Map items to JSX elements

↓

Assign unique key to each element

↓

React uses keys to track elements

↓

On update: compare keys to detect changes

↓

Update only changed elements in DOM

React uses keys to identify list items uniquely so it can update only changed elements efficiently.

Execution Sample

React

const items = ['A', 'B', 'C'];
return (
  <ul>
    {items.map(item => <li key={item}>{item}</li>)}
  </ul>
);

This code renders a list of items with unique keys for each list element.

Execution Table

Step	Action	JSX Element	Key Assigned	React Behavior
1	Start rendering list	No elements yet	No keys	Prepare to create elements
2	Map item 'A'	<li>A</li>	'A'	Create element with key 'A'
3	Map item 'B'	<li>B</li>	'B'	Create element with key 'B'
4	Map item 'C'	<li>C</li>	'C'	Create element with key 'C'
5	Render complete	<ul> with 3 <li>	Keys 'A', 'B', 'C'	React tracks elements by keys
6	Update list to ['A', 'C', 'D']	Map new items	'A', 'C', 'D'	React compares keys, reuses 'A' and 'C', adds 'D', removes 'B'

💡 Rendering ends after all list items are processed and keys assigned

Variable Tracker

Variable	Start	After 1	After 2	After 3	After Update
items	['A', 'B', 'C']	['A', 'B', 'C']	['A', 'B', 'C']	['A', 'B', 'C']	['A', 'C', 'D']
keys	[]	['A']	['A', 'B']	['A', 'B', 'C']	['A', 'C', 'D']

Key Moments - 2 Insights

Why do keys need to be unique among siblings?

Keys must be unique so React can correctly identify which element changed, added, or removed, as shown in execution_table step 6 where React compares keys to update the list.

What happens if keys are missing or not unique?

React may reuse or reorder elements incorrectly, causing bugs or inefficient updates, because it cannot track elements properly without unique keys (see execution_table step 5).

Visual Quiz - 3 Questions

Look at the execution_table at step 3. What key is assigned to the JSX element?

A 'A'

B 'C'

C 'B'

D No key assigned

💡 Hint

Check the 'Key Assigned' column at step 3 in execution_table

At which step does React detect that an item was removed from the list?

A Step 4

B Step 6

C Step 5

D React never detects removals

💡 Hint

Look at the 'React Behavior' column in execution_table step 6

If the keys were not unique, how would React's update behavior change?

A React might reuse wrong elements causing bugs

B React would update only changed elements correctly

C React would ignore the list entirely

D React would throw a syntax error

💡 Hint

Refer to key_moments about importance of unique keys

Concept Snapshot

Keys in React:
- Used in lists to uniquely identify elements
- Assigned via 'key' prop in JSX
- Help React track changes efficiently
- Keys must be unique among siblings
- Missing or duplicate keys cause update bugs

Full Transcript

In React, keys are special strings assigned to elements in a list to help React identify which items have changed, been added, or removed. When rendering a list, React maps each item to a JSX element and assigns a unique key. During updates, React compares these keys to update only the necessary elements in the DOM, improving performance and avoiding bugs. Keys must be unique among siblings; otherwise, React may confuse elements and cause unexpected behavior. This visual trace shows how keys are assigned step-by-step and how React uses them to track changes efficiently.

Practice

1. Why does React require keys when rendering lists with map()?

easy

A. To uniquely identify each list item for efficient updates

B. To style each list item differently

C. To sort the list items automatically

D. To prevent the list from rendering

Solution

1. Step 1: Understand React's list rendering

   React uses keys to track each item in a list so it can update only changed items instead of re-rendering the whole list.

2. Step 2: Identify the purpose of keys

   Keys must be unique and stable to help React identify which items changed, were added, or removed.

3. Final Answer:

   To uniquely identify each list item for efficient updates -> Option A

4. Quick Check:

   Keys = Unique IDs for list items [OK]

Hint: Keys uniquely identify list items for React updates [OK]

Common Mistakes:

• Thinking keys are for styling
• Believing keys sort the list
• Assuming keys prevent rendering

2. Which of the following is the correct way to assign keys in a React list?

easy

A. {items.map(item => <li key={index}>{item.name}</li>)}

B. {items.map(item => <li key={item.id}>{item.name}</li>)}

C. {items.map(item => <li key={Math.random()}>{item.name}</li>)}

D. {items.map(item => <li>{item.name}</li>)}

Solution

1. Step 1: Check key uniqueness and stability

   Using item.id ensures each key is unique and stable across renders.

2. Step 2: Evaluate other options

   Using index or Math.random() can cause unstable keys leading to rendering bugs. Omitting keys causes React warnings.

3. Final Answer:

   {items.map(item => <li key={item.id}>{item.name}</li>)} -> Option B

4. Quick Check:

   Use stable unique IDs as keys [OK]

Hint: Use unique stable IDs, not index or random, for keys [OK]

Common Mistakes:

• Using array index as key when list changes
• Using random values for keys
• Not providing any key

3. What will be the output in the console when this React code runs?

const items = [
  { id: 1, name: 'Apple' },
  { id: 2, name: 'Banana' },
  { id: 3, name: 'Cherry' }
];

const list = items.map(item => <li key={item.id}>{item.name}</li>);
console.log(list.length);

medium

A. 3

B. undefined

C. 0

D. Error

Solution

1. Step 1: Understand the map function output

   The map creates an array of 3 <li> React elements, one for each item.

2. Step 2: Check the length of the array

   The array list has 3 elements, so list.length is 3.

3. Final Answer:

   3 -> Option A

4. Quick Check:

   Array length equals number of items mapped [OK]

Hint: map returns array same length as input [OK]

Common Mistakes:

• Confusing React elements with strings
• Expecting undefined from map
• Thinking keys affect array length

4. Identify the problem in this React code snippet:

const items = ['A', 'B', 'C'];

return (
  <ul>
    {items.map((item, index) => (
      <li key={index}>{item}</li>
    ))}
  </ul>
);

medium

A. map function syntax is incorrect

B. Missing unique key prop causes error

C. Using index as key can cause bugs if list changes

D. List items should be wrapped in a div

Solution

1. Step 1: Analyze key usage

   Using array index as key works only if list never changes order or items.

2. Step 2: Understand potential bugs

   If items are added, removed, or reordered, React may reuse wrong elements causing UI bugs.

3. Final Answer:

   Using index as key can cause bugs if list changes -> Option C

4. Quick Check:

   Index keys cause bugs on list changes [OK]

Hint: Avoid index keys if list can reorder or change [OK]

Common Mistakes:

• Thinking index keys are always safe
• Believing missing keys cause syntax errors
• Assuming map syntax is wrong

5. You have a list of users with possible duplicate names:

const users = [
  { id: 1, name: 'Sam' },
  { id: 2, name: 'Alex' },
  { id: 3, name: 'Sam' }
];

return (
  <ul>
    {users.map(user => <li key={user.name}>{user.name}</li>)}
  </ul>
);

What problem might occur and how to fix it?

hard

A. Wrap list in a fragment to fix duplicate keys

B. No problem; keys can be duplicate if names match

C. Keys must be numbers; convert names to numbers

D. Duplicate keys from same names cause rendering bugs; use user.id as key

Solution

1. Step 1: Identify duplicate keys

   Using user.name as key causes duplicates because 'Sam' appears twice.

2. Step 2: Fix by using unique stable keys

   Use user.id which is unique for each user to avoid React key conflicts.

3. Final Answer:

   Duplicate keys from same names cause rendering bugs; use user.id as key -> Option D

4. Quick Check:

   Keys must be unique; use unique IDs [OK]

Hint: Keys must be unique; avoid duplicates like same names [OK]

Common Mistakes:

• Assuming keys can be duplicated
• Thinking keys must be numeric only
• Trying to fix keys by wrapping in fragments