State re-render behavior in React - Cheat Sheet & Quick Revision

Recall & Review

beginner

What happens in React when you update a component's state using useState?

React schedules a re-render of that component. The component function runs again, and React updates the UI to reflect the new state.

intermediate

Does React re-render a component if the state value is set to the same value it already has?

No. React compares the new state with the current state using Object.is. If they are the same, React skips the re-render to improve performance.

beginner

Why should you avoid directly mutating state in React?

Direct mutation does not change the state reference, so React may not detect a change and skip re-rendering. Always use the state setter function to update state immutably.

intermediate

How does React batch multiple state updates inside event handlers?

React groups multiple state updates in event handlers into one re-render to improve performance, so the component only re-renders once after all updates.

beginner

What is the role of useEffect in relation to state changes and re-rendering?

useEffect runs after the component renders. It can react to state changes to perform side effects like fetching data or updating the DOM outside React.

What triggers a React component to re-render?

A Updating the component's state using the setter function

B Changing a variable outside the component

C Calling a function inside the component without state change

D Updating a CSS file

Only updating the component's state with the setter function triggers React to re-render that component.

If you call the state setter with the same value as current state, what happens?

A React skips the re-render

B React re-renders the component anyway

C React throws an error

D React resets the state to initial value

React compares the new and current state and skips re-render if they are the same to optimize performance.

Why is it important to avoid mutating state directly?

A It causes React to re-render twice

B React may not detect the change and skip re-render

C It makes the app slower

D It causes syntax errors

Direct mutation does not change the state reference, so React may not detect the change and skip re-rendering.

How does React handle multiple state updates inside an event handler?

A It re-renders after each update

B It ignores all but the last update

C It crashes the app

D It batches updates and re-renders once

React batches multiple state updates inside event handlers to re-render only once for better performance.

When does useEffect run in relation to state changes?

A Before the component renders

B During the render

C After the component renders

D Only on initial load

useEffect runs after the component renders and can respond to state changes to perform side effects.

Explain how React decides when to re-render a component after a state update.

Think about how React checks if the state really changed before re-rendering.

Describe how React batches multiple state updates and why this is useful.

Imagine updating your shopping list several times quickly and React only updating the screen once.

Practice

1. What happens in React when you update a component's state using setState?

easy

A. React re-renders that component and its children to update the UI.

B. React reloads the entire page to reflect the changes.

C. React ignores the change unless the component is a class component.

D. React only updates the state internally without changing the UI.

Solution

1. Step 1: Understand what setState does

   Using setState tells React that the component's state has changed and it needs to update the UI.

2. Step 2: Know React's rendering behavior

   React re-renders the component where state changed and all its child components to reflect the new state.

3. Final Answer:

   React re-renders that component and its children to update the UI. -> Option A

4. Quick Check:

   State change triggers re-render = B [OK]

Hint: State change triggers re-render of component and children [OK]

Common Mistakes:

• Thinking React reloads the whole page
• Believing state changes don't affect functional components
• Assuming UI doesn't update automatically

2. Which of the following is the correct way to update state in a React functional component?

easy

A. this.state.count = 1;

B. updateState({count: 1});

C. count = 1;

D. setCount(1);

Solution

1. Step 1: Recall how state is updated in functional components

   Functional components use the useState hook, which returns a setter function like setCount.

2. Step 2: Identify the correct syntax

   Calling setCount(1) updates the state and triggers a re-render.

3. Final Answer:

   setCount(1); -> Option D

4. Quick Check:

   Use setter function from useState = D [OK]

Hint: Use the setter function from useState to update state [OK]

Common Mistakes:

• Trying to assign state directly like a variable
• Using this.state in functional components
• Using non-existent functions like updateState

3. Consider this React component code:

function Counter() {
  const [count, setCount] = React.useState(0);
  React.useEffect(() => {
    console.log('Rendered with count:', count);
  });
  return  setCount(count + 1)}>Click {count};
}

What will be logged to the console after clicking the button twice?

medium

A. 'Rendered with count: 1' then 'Rendered with count: 2'

B. 'Rendered with count: 0' only once

C. 'Rendered with count: 2' only once

D. No logs will appear

Solution

1. Step 1: Understand useEffect without dependencies

   Without a dependency array, useEffect runs after every render.

2. Step 2: Trace state changes on clicks

   Initial count is 0. Clicking once sets count to 1, triggering a render and logging 'Rendered with count: 1'. Clicking again sets count to 2, triggering another render and logging 'Rendered with count: 2'.

3. Final Answer:

   'Rendered with count: 1' then 'Rendered with count: 2' -> Option A

4. Quick Check:

   State updates cause re-render and useEffect logs each time = A [OK]

Hint: useEffect without deps runs after every render [OK]

Common Mistakes:

• Thinking useEffect runs only once
• Assuming logs show initial state only
• Ignoring that state updates cause re-renders

4. What is wrong with this React code snippet?

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

medium

A. useState hook is used incorrectly; it needs two arguments.

B. Directly assigning to state variable does not update state or trigger re-render.

C. The function update should be async to update state.

D. The button should use onChange instead of onClick.

Solution

1. Step 1: Identify how state is updated

   State variables from useState are read-only. Direct assignment like value = value + 1 does not update React state.

2. Step 2: Understand correct state update method

   State must be updated using the setter function setValue to trigger re-render.

3. Final Answer:

   Directly assigning to state variable does not update state or trigger re-render. -> Option B

4. Quick Check:

   State updates require setter function = C [OK]

Hint: Never assign state variable directly; use setter function [OK]

Common Mistakes:

• Assigning state variable directly
• Confusing event handlers like onChange vs onClick
• Thinking useState needs two arguments

5. You have a parent component that renders a child component. The parent updates its state with setParentState. Which components re-render when the parent's state changes?

hard

A. Only the child component re-renders; the parent does not.

B. Only the parent component re-renders; the child does not.

C. Both the parent and child components re-render.

D. Neither component re-renders automatically.

Solution

1. Step 1: Understand React's re-render on state change

   When a parent component's state changes, React re-renders that parent component.

2. Step 2: Know child component rendering behavior

   Since the child is rendered inside the parent, React also re-renders the child unless memoization or other optimizations are used.

3. Final Answer:

   Both the parent and child components re-render. -> Option C

4. Quick Check:

   Parent state change re-renders parent and children = A [OK]

Hint: Parent state change re-renders parent and children by default [OK]

Common Mistakes:

• Thinking child won't re-render automatically
• Assuming only child re-renders
• Believing no re-render happens without explicit calls