Re-rendering behavior in React - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a state variable using React hooks.

React

const [count, setCount] = [1](0);

Drag options to blanks, or click blank then click option'

AuseRef

BuseState

CuseEffect

DuseContext

Attempts:

3 left

💡 Hint

Common Mistakes

Using useEffect instead of useState for state variables.

Trying to update state without a setter function.

The useState hook creates a state variable and a function to update it, which triggers re-rendering.

2fill in blank

medium

Complete the code to run a side effect after every render.

React

useEffect(() => { console.log('Rendered'); }, [1]);

Drag options to blanks, or click blank then click option'

A[]

B[count]

Cnull

Dundefined

Attempts:

3 left

💡 Hint

Common Mistakes

Passing an empty array to run effect only once.

Passing a specific state variable to run effect only when it changes.

Omitting the dependency array or passing undefined causes useEffect to run after every render.

3fill in blank

hard

Fix the error in the code that causes unnecessary re-renders.

React

const memoizedValue = useMemo(() => computeExpensiveValue(), [1]);

Drag options to blanks, or click blank then click option'

A[memoizedValue]

B[computeExpensiveValue]

C[]

Dnull

Attempts:

3 left

💡 Hint

Common Mistakes

Leaving dependencies undefined causing recomputation every render.

Including the function itself as a dependency causing infinite loops.

Passing an empty array ensures the expensive computation runs only once, preventing unnecessary re-renders.

4fill in blank

hard

Fill both blanks to prevent unnecessary re-renders by memoizing the callback and its dependencies.

React

const handleClick = useCallback(() => { setCount(count [1] 1); }, [2]);

Drag options to blanks, or click blank then click option'

A+

B-

C[count]

D[]

Attempts:

3 left

💡 Hint

Common Mistakes

Using an empty dependency array causing stale closures.

Using subtraction instead of addition changing the logic.

The callback increments count by 1 and depends on count, so it must be included in the dependency array.

5fill in blank

hard

Fill all three blanks to create a memoized list of even numbers from props.numbers.

React

const evenNumbers = useMemo(() => props.numbers.filter(num => num [1] 2 === 0), [2]); const count = evenNumbers[3]length;

Drag options to blanks, or click blank then click option'

A%

B[props.numbers]

C.

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using equality operator instead of modulo for even check.

Missing dependency array causing stale memo.

Using wrong syntax to access length property.

The modulo operator % checks for even numbers. The dependency array includes props.numbers so memo updates when numbers change. The dot . accesses the length property.

Practice

1. Which of the following causes a React component to re-render?

easy

A. When a variable inside the component function changes but state does not

B. When the component's state changes using a state setter like setState or useState setter

C. When the component's CSS styles change

D. When the browser window is resized

Solution

1. Step 1: Understand React's re-render triggers

   React re-renders a component when its state or props change, not just any variable or style change.

2. Step 2: Identify the correct trigger

   Using setState or the setter from useState updates state and triggers re-rendering.

3. Final Answer:

   When the component's state changes using a state setter like setState or useState setter -> Option B

4. Quick Check:

   State change triggers re-render = B [OK]

Hint: State or props change triggers re-rendering in React [OK]

Common Mistakes:

• Thinking local variable changes cause re-render
• Assuming style changes trigger re-render
• Believing window resize triggers component re-render

2. Which of the following is the correct way to update state and trigger a re-render in a React functional component?

easy

A. this.state.count = 5;

B. count = 5;

C. updateState(count = 5);

D. setCount(5);

Solution

1. Step 1: Recall state update syntax in functional components

   In React functional components, state is updated using the setter function returned by useState, e.g., setCount.

2. Step 2: Identify the correct syntax

   Direct assignment like this.state.count = 5 or count = 5 does not trigger re-render. Only calling setCount(5) updates state properly.

3. Final Answer:

   setCount(5); -> Option D

4. Quick Check:

   Use setter function to update state = C [OK]

Hint: Use setter from useState to update state, not direct assignment [OK]

Common Mistakes:

• Trying to assign state directly
• Using undefined functions like updateState
• Confusing class component syntax with functional

3. Consider this React functional component:

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

What will be logged to the console after clicking the button three times?

medium

A. Render: 0, Render: 1, Render: 2, Render: 3

B. Render: 0, Render: 1

C. Render: 3 only

D. Render: 1, Render: 2, Render: 3

Solution

1. Step 1: Understand initial render and state updates

   Initially, the component renders with count = 0 and logs 'Render: 0'. Each button click calls setCount(count + 1), updating state and causing re-render.

2. Step 2: Trace each click and render

   After first click, count becomes 1 and logs 'Render: 1'. Second click updates count to 2 and logs 'Render: 2'. Third click updates count to 3 and logs 'Render: 3'.

3. Final Answer:

   Render: 0, Render: 1, Render: 2, Render: 3 -> Option A

4. Quick Check:

   Each state update triggers render log = A [OK]

Hint: Each state update triggers a new render and console log [OK]

Common Mistakes:

• Ignoring initial render log
• Assuming only last render logs
• Thinking state updates batch without intermediate renders

4. Given this React component:

function Example() {
  const [value, setValue] = React.useState(0);
  function update() {
    value = value + 1;
  }
  return <button onClick={update}>Value: {value}</button>;
}

Why does clicking the button NOT update the displayed value?

medium

A. Because direct assignment to value does not update state or trigger re-render

B. Because the update function is not called on click

C. Because the initial state is zero and never changes

D. Because React does not allow state updates inside event handlers

Solution

1. Step 1: Identify how state updates trigger re-render

   React re-renders when state is updated via the setter function, not by direct variable assignment.

2. Step 2: Analyze the update function

   The function assigns value = value + 1 directly, which changes a local variable but does not update React state or cause re-render.

3. Final Answer:

   Because direct assignment to value does not update state or trigger re-render -> Option A

4. Quick Check:

   State must be updated via setter to re-render = A [OK]

Hint: Always use state setter to update state, not direct assignment [OK]

Common Mistakes:

• Thinking direct assignment updates state
• Assuming event handler is not called
• Believing React forbids state updates in handlers

5. You have a parent component passing a prop count to a child component. The child uses React.memo to avoid unnecessary re-renders. Which of these changes will cause the child to re-render?

hard

A. The parent re-renders but passes the same count value as before

B. A variable inside the child component function changes but state does not

C. The parent passes a new count value different from before

D. The parent changes an unrelated state but count stays the same

Solution

1. Step 1: Understand React.memo behavior

   React.memo prevents re-render if props are shallowly equal. If props change, it re-renders.

2. Step 2: Analyze each option

   A: Same count means props equal, no re-render.
   B: Local variable change does not update state or props, no re-render.
   C: Unrelated state change in parent does not affect child's props if count same.
   D: New count value means props changed, triggers re-render.

3. Final Answer:

   The parent passes a new count value different from before -> Option C

4. Quick Check:

   Prop change triggers React.memo re-render = D [OK]

Hint: React.memo re-renders only if props change shallowly [OK]

Common Mistakes:

• Thinking parent re-render always triggers child re-render
• Ignoring prop equality in React.memo
• Thinking local variable changes cause re-render