Common lifting state patterns in React - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does "lifting state up" mean in React?

It means moving shared state from child components to their closest common parent so that the parent can manage the state and pass it down as props.

beginner

Why do we lift state up in React?

We lift state up to keep data consistent between components that need to share or sync the same information.

beginner

In a parent component, how do you pass state and state updater to child components?

You pass the state value as a prop and the state updater function as another prop, so children can read and update the state via callbacks.

intermediate

What is a common pattern when two sibling components need to share state?

Lift the shared state up to their nearest common parent and pass the state and updater down to both siblings as props.

intermediate

How can lifting state up improve component reusability?

By moving state management to a parent, child components become simpler and focused on UI, making them easier to reuse with different data.

What is the main reason to lift state up in React?

A To create more components

B To make components heavier

C To avoid using props

D To share state between components

Lifting state up helps share state between components that need the same data.

Where should you lift state up to when two sibling components need to share data?

A To the nearest common parent component

B To the child component

C To the root of the app always

D To a random unrelated component

The nearest common parent is the best place to hold shared state for siblings.

How do child components update lifted state in the parent?

A By calling a state updater function passed as a prop

B By directly changing the parent's state

C By using global variables

D By reloading the page

Parents pass down a function to update state, which children call to change the state.

What happens if you don’t lift state up when needed?

A State is shared globally

B Components may have inconsistent or out-of-sync data

C You get automatic data sharing

D The app runs faster

Without lifting state, components can have different versions of the same data causing bugs.

Which React hook is commonly used to hold state that you might lift up?

A useRef

B useEffect

C useState

D useMemo

useState is the hook to create and manage state in functional components.

Explain how lifting state up helps two sibling components share data in React.

Think about where the shared state lives and how siblings get access.

Describe the steps to lift state up from a child component to a parent component in React.

Focus on how state and functions move between parent and child.

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