Common lifting state patterns in React - Step-by-Step Execution

Concept Flow - Common lifting state patterns

Child A needs state

↓

State lifted to Parent

↓

Parent holds state

↓

Parent passes state and setter to Child A

↓

Child A updates state via setter

↓

Parent updates state and re-renders

↓

Updated state passed down to Child A and Child B

↓

Child B uses updated state

State is moved up to the parent so multiple children can share and update it, keeping data in sync.

Execution Sample

React

import React, { useState } from 'react';

function Parent() {
  const [count, setCount] = useState(0);
  return (
    <>
      <ChildA count={count} setCount={setCount} />
      <ChildB count={count} />
    </>
  );
}

Parent component holds count state and passes it with setter to ChildA and count to ChildB.

Execution Table

Step	Action	State Before	State After	Component Rendered	Output/Behavior
1	Parent initializes count=0	count=undefined	count=0	Parent	Renders ChildA and ChildB with count=0
2	ChildA renders with count=0	count=0	count=0	ChildA	Shows count=0, has button to increment
3	ChildB renders with count=0	count=0	count=0	ChildB	Shows count=0
4	User clicks increment in ChildA	count=0	count=0	ChildA	Calls setCount(1)
5	Parent updates count to 1	count=0	count=1	Parent	Triggers re-render of Parent and children
6	ChildA re-renders with count=1	count=1	count=1	ChildA	Shows updated count=1
7	ChildB re-renders with count=1	count=1	count=1	ChildB	Shows updated count=1
8	No more actions	count=1	count=1	None	State stable, UI updated

💡 User stops interaction; state is stable and UI reflects latest count.

Variable Tracker

Variable	Start	After Step 1	After Step 4	After Step 5	Final
count	undefined	0	0	1	1

Key Moments - 3 Insights

Why does ChildB update even though it doesn't have a setter?

Because Parent holds the state and passes count as a prop to ChildB, when Parent updates count, ChildB re-renders with new value (see steps 5-7).

Why do we lift state to Parent instead of keeping it in ChildA?

Lifting state to Parent allows multiple children (ChildA and ChildB) to share the same state and stay in sync, as shown in the flow from step 1 to 7.

What happens if ChildA calls setCount with the same value as current state?

React will not re-render because state didn't change, so ChildB won't update either (not shown in table but important to know).

Visual Quiz - 3 Questions

Look at the execution table, what is the value of count after step 5?

A 1

B 0

C undefined

D 2

💡 Hint

Check the 'State After' column at step 5 in the execution_table.

At which step does ChildB first render with the updated count?

A Step 6

B Step 7

C Step 3

D Step 4

💡 Hint

Look for ChildB rendering with count=1 in the execution_table rows.

If we remove setCount from ChildA props, what changes in the execution?

A ChildB stops rendering

B Parent state updates automatically

C ChildA cannot update count, so count stays 0

D No change, everything works the same

💡 Hint

Refer to step 4 where ChildA calls setCount to update state.

Concept Snapshot

Lifting state means moving state up to a common parent.
Parent holds the state and passes it down as props.
Children receive state and setter functions as needed.
Updating state in parent triggers re-render of all children.
This keeps shared data consistent across components.

Full Transcript

In React, lifting state means moving the state from a child component up to their common parent. This allows multiple children to share and update the same state. The parent holds the state and passes it down as props to children. One child can receive the state and a setter function to update it. When the setter is called, the parent updates the state and re-renders. This causes all children receiving that state to update their display. This pattern keeps data consistent and synchronized across components that need to share it.

Practice

1. What is the main reason to lift state up in React?
lifting state means moving state to a common parent component.

easy

A. To make components independent

B. To share state between sibling components

C. To avoid using props

D. To store state only in child components

Solution

1. Step 1: Understand lifting state concept

   Lifting state means moving state to a common parent so multiple children can access it.

2. Step 2: Identify the purpose of lifting state

   This is done to share state between sibling components and keep data in sync.

3. Final Answer:

   To share state between sibling components -> Option B

4. Quick Check:

   Lifting state = sharing state [OK]

Hint: Lifting state shares data between siblings via parent [OK]

Common Mistakes:

• Thinking lifting state makes components independent
• Believing lifting state removes props usage
• Assuming state stays only in children

2. Which of the following is the correct way to pass state and its updater function from a parent to a child component in React?

easy

A. <Child state={state} setState={setState} />

B. <Child state=setState />

C. <Child setState={state} state={setState} />

D. <Child state=setState() />

Solution

1. Step 1: Recall React props syntax

   Props are passed as name={value}. To pass state and updater, use state={state} and setState={setState}.

2. Step 2: Check each option's syntax

   <Child state={state} setState={setState} /> correctly passes both as props. Others misuse assignment or call functions incorrectly.

3. Final Answer:

   <Child state={state} setState={setState} /> -> Option A

4. Quick Check:

   Props pass state and updater correctly [OK]

Hint: Props use curly braces for variables [OK]

Common Mistakes:

• Passing functions without curly braces
• Calling updater functions instead of passing them
• Swapping state and updater names

3. Given this parent component code:

function Parent() {
  const [count, setCount] = React.useState(0);
  return (
    <>
      <Display count={count} />
      <Button onClick={() => setCount(count + 1)} />
    </>
  );
}

What will happen when the Button is clicked?

medium

A. Nothing happens because count is not updated

B. The Button component will re-render but count stays the same

C. The count displayed by Display increases by 1

D. An error occurs because setCount is not passed to Button

Solution

1. Step 1: Understand state and props flow

   The Parent holds count state and passes count to Display and an onClick handler to Button.

2. Step 2: Analyze Button click effect

   Clicking Button calls setCount(count + 1), updating state and causing Parent to re-render with new count.

3. Final Answer:

   The count displayed by Display increases by 1 -> Option C

4. Quick Check:

   State update triggers re-render and display update [OK]

Hint: State update in parent re-renders children with new props [OK]

Common Mistakes:

• Thinking Button needs count prop to update
• Believing setCount must be passed to Display
• Assuming no re-render happens on state change

4. Identify the error in this code snippet where a parent tries to lift state:

function Parent() {
  const [value, setValue] = React.useState('');
  return <Child value={value} setValue={value} />;
}

medium

A. setValue prop is incorrectly assigned the state value instead of the updater function

B. value state is not initialized properly

C. Child component is missing parentheses

D. React.useState should be React.state

Solution

1. Step 1: Check props passed to Child

   Parent passes value={value} correctly but setValue={value} incorrectly passes the state value instead of the updater function.

2. Step 2: Understand correct usage

   setValue should be passed as setValue={setValue} to allow Child to update state.

3. Final Answer:

   setValue prop is incorrectly assigned the state value instead of the updater function -> Option A

4. Quick Check:

   Updater function must be passed, not state value [OK]

Hint: Pass updater function, not state value, as setState prop [OK]

Common Mistakes:

• Confusing state variable with updater function
• Forgetting curly braces around variables
• Assuming React.useState is incorrect

5. You have two sibling components, InputA and InputB, both need to update and display the same text value. Which pattern correctly lifts state to their parent to keep them in sync?

hard

A. Use local variables in siblings without state

B. Store text state separately in each sibling, update independently

C. Store text state in one sibling and pass it down to the other sibling

D. Store text state in parent, pass text and setText to both siblings as props

Solution

1. Step 1: Understand shared state need

   Both siblings must show and update the same text, so state must be shared.

2. Step 2: Apply lifting state pattern

   Lift text state to their common parent and pass text and setText as props to both siblings.

3. Step 3: Evaluate other options

   Storing state separately or in one sibling breaks sync; local variables don't persist or trigger re-renders.

4. Final Answer:

   Store text state in parent, pass text and setText to both siblings as props -> Option D

5. Quick Check:

   Lift state to parent for shared updates [OK]

Hint: Lift shared state to parent, pass state and updater down [OK]

Common Mistakes:

• Keeping separate states in siblings causing out-of-sync
• Passing state only one way between siblings
• Using local variables instead of state