Callback functions for state updates in React - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a callback function in React state updates?

A callback function is a function passed to the state updater that receives the previous state and returns the new state. It helps update state based on the latest value.

beginner

Why use a callback function for updating state instead of a direct value?

Using a callback ensures you get the latest state value, especially when updates happen quickly or asynchronously, avoiding bugs from stale state.

beginner

Show a simple example of using a callback function with useState.

Example: setCount(prevCount => prevCount + 1); This adds 1 to the current count safely.

intermediate

What problem does the callback function solve in concurrent React updates?

It prevents race conditions by always using the freshest state value, so multiple updates don't overwrite each other incorrectly.

intermediate

Can you use a callback function with useState to update complex state objects?

Yes, you can update parts of an object safely by returning a new object based on the previous state inside the callback.

What argument does the callback function receive when updating state with useState?

A The new state value

B The previous state value

C The component props

D The event object

The callback function receives the previous state value to compute the new state.

Why is using a callback function safer for state updates in React?

A It always uses the latest state value

B It runs faster

C It prevents rendering

D It avoids using hooks

Using a callback ensures the update uses the freshest state, avoiding bugs from stale values.

Which syntax correctly updates state using a callback function?

A setCount(() => 1)

B setCount(count + 1)

C setCount(prev => prev + 1)

D setCount(prevCount)

The callback receives previous state and returns the new state, like setCount(prev => prev + 1).

When might you need to use a callback function for state updates?

A When new state depends on previous state

B When setting static values

C When updating props

D When rendering JSX

Use a callback when the new state depends on the previous state value.

What happens if you update state directly without a callback in rapid updates?

A React crashes

B The component unmounts

C State updates instantly

D You might get stale or incorrect state

Direct updates can cause stale state bugs if multiple updates happen quickly.

Explain how callback functions help update React state safely.

Think about how React batches updates and why previous state matters.

Describe a scenario where using a callback function for state update is necessary.

Consider when you want to add 1 to a counter multiple times quickly.

Practice

1. Why should you use a callback function when updating state in React with useState?

easy

A. Because it safely uses the previous state value to calculate the new state.

B. Because it makes the component render twice automatically.

C. Because it prevents the component from updating.

D. Because it allows you to update multiple states at once.

Solution

1. Step 1: Understand state updates in React

   State updates can be asynchronous, so relying on the current state value directly can cause bugs.

2. Step 2: Use callback function to access previous state

   The callback function receives the previous state safely and returns the new state, ensuring correct updates.

3. Final Answer:

   Because it safely uses the previous state value to calculate the new state. -> Option A

4. Quick Check:

   Callback uses previous state = safe update [OK]

Hint: Use callback to get previous state safely for updates [OK]

Common Mistakes:

• Updating state directly without callback causes stale values
• Thinking callback triggers extra renders
• Believing callback merges multiple states automatically

2. Which of the following is the correct syntax to update state using a callback function with useState?

easy

A. setCount(count + 1);

B. setCount(prevCount => prevCount + 1);

C. setCount(() => count + 1);

D. setCount(prevCount + 1);

Solution

1. Step 1: Identify correct callback syntax

   The callback function receives previous state as an argument and returns the new state.

2. Step 2: Check each option

   setCount(prevCount => prevCount + 1); uses prevCount => prevCount + 1, which is the correct callback form.

3. Final Answer:

   setCount(prevCount => prevCount + 1); -> Option B

4. Quick Check:

   Callback syntax = setState(prev => new) [OK]

Hint: Callback syntax always uses previous state parameter [OK]

Common Mistakes:

• Passing new state directly without function
• Using arrow function without parameter
• Trying to add number outside callback

3. What will be the output after clicking the button twice in this React component?

function Counter() {
  const [count, setCount] = React.useState(0);
  function increment() {
    setCount(prev => prev + 1);
  }
  return (
    <button onClick={increment}>Count: {count}</button>
  );
}

medium

A. Count: 2

B. Count: NaN

C. Count: 0

D. Count: 1

Solution

1. Step 1: Understand initial state and increment function

   Initial count is 0. Each click calls increment which updates state by adding 1 to previous count.

2. Step 2: Calculate state after two clicks

   First click: 0 + 1 = 1. Second click: 1 + 1 = 2.

3. Final Answer:

   Count: 2 -> Option A

4. Quick Check:

   Two increments = count 2 [OK]

Hint: Each click adds 1 to previous count using callback [OK]

Common Mistakes:

• Assuming state updates are batched incorrectly
• Using stale count value without callback
• Expecting count to reset after each click

4. Identify the error in this React state update code:

const [value, setValue] = React.useState(0);
function update() {
  setValue(value + 1);
  setValue(value + 1);
}

medium

A. setValue cannot be called twice in one function.

B. Syntax error: missing callback function.

C. State updates will be batched and only increase by 1, not 2.

D. State will reset to 0 after update.

Solution

1. Step 1: Analyze multiple state updates with direct value

   Both calls use the same stale value (0), so both set to 1.

2. Step 2: Understand batching behavior

   React batches updates, so final state is 1, not 2.

3. Final Answer:

   State updates will be batched and only increase by 1, not 2. -> Option C

4. Quick Check:

   Direct state updates = stale value, batched result [OK]

Hint: Multiple direct updates use stale state, use callback instead [OK]

Common Mistakes:

• Thinking setValue calls add up automatically
• Believing syntax error occurs without callback
• Assuming state resets unexpectedly

5. You want to toggle a boolean state isOpen in React. Which is the best way to update it safely when the new state depends on the old state?

hard

A. setIsOpen(false);

B. setIsOpen(!isOpen);

C. setIsOpen(true);

D. setIsOpen(prev => !prev);

Solution

1. Step 1: Understand toggling boolean state

   Toggling means switching from true to false or false to true based on previous state.

2. Step 2: Choose callback to avoid stale state

   Using prev => !prev ensures the toggle uses the latest state safely.

3. Final Answer:

   setIsOpen(prev => !prev); -> Option D

4. Quick Check:

   Toggle boolean safely = callback with previous state [OK]

Hint: Toggle booleans with callback using previous state [OK]

Common Mistakes:

• Using direct negation causes stale state bugs
• Setting fixed true or false instead of toggling
• Not using callback for dependent state updates