Updating phase in React - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to update state correctly in a React functional component.

React

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

function increment() {
  setCount([1]);
}

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

Acount + 1

Bcount - 1

Ccount * 2

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using a fixed number like 0 resets the count.

Subtracting 1 decreases the count instead of increasing.

To update state by increasing the count, use count + 1 inside setCount.

2fill in blank

medium

Complete the code to run a side effect after the component updates.

React

useEffect(() => {
  console.log('Count updated:', count);
}, [[1]]);

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

AsetCount

BuseState

Ccount

Dincrement

Attempts:

3 left

💡 Hint

Common Mistakes

Putting the setter function instead of the state variable.

Leaving the dependency array empty, so effect runs only once.

The effect runs when count changes, so it must be in the dependency array.

3fill in blank

hard

Fix the error in the state update function to avoid stale state.

React

setCount([1] => [1] + 1);

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

AprevCount

Bcount

Cstate

Dvalue

Attempts:

3 left

💡 Hint

Common Mistakes

Using the state variable directly can cause stale updates.

Not using a function causes race conditions in updates.

Using a function with a parameter like prevCount ensures you get the latest state value.

4fill in blank

hard

Fill both blanks to create a controlled input that updates state on change.

React

const [name, setName] = useState('');

<input value=[1] onChange={e => setName([2])} />

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

Aname

Be.target.value

CsetName

De.value

Attempts:

3 left

💡 Hint

Common Mistakes

Using e.value instead of e.target.value.

Not setting the input's value to the state variable.

The input's value is controlled by name. On change, update state with e.target.value.

5fill in blank

hard

Fill all three blanks to update multiple state values in an object using the spread operator.

React

const [form, setForm] = useState({ email: '', password: '' });

setForm({ ...[1], [2]: [3] });

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

Aform

Bemail

Ce.target.value

Dpassword

Attempts:

3 left

💡 Hint

Common Mistakes

Not spreading the old state causes loss of other fields.

Mixing up field names or using wrong event properties.

Use the spread operator on form to keep existing values, then update the password field with the new value from e.target.value.

Practice

1. What happens during the updating phase in a React component?

easy

A. The component is removed from the screen

B. The component is created for the first time

C. The component's styles are applied

D. The component re-renders when state or props change

Solution

1. Step 1: Understand React component lifecycle phases

   The updating phase happens after the initial render when state or props change.

2. Step 2: Identify what triggers re-rendering

   State or props changes cause React to re-render the component to update the UI.

3. Final Answer:

   The component re-renders when state or props change -> Option D

4. Quick Check:

   Updating phase = re-render on state/props change [OK]

Hint: Updating phase means re-render on state or props change [OK]

Common Mistakes:

• Confusing updating with mounting or unmounting phases
• Thinking styles apply only during updating
• Believing updating happens without state or props change

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

easy

A. this.setState({ count: count + 1 })

B. setCount(count + 1)

C. updateState(count + 1)

D. changeState({ count: count + 1 })

Solution

1. Step 1: Identify state update method in functional components

   Functional components use the setter function from useState, e.g., setCount.

2. Step 2: Check syntax correctness

   setCount(count + 1) correctly updates the state by adding 1.

3. Final Answer:

   setCount(count + 1) -> Option B

4. Quick Check:

   Use setter from useState to update state [OK]

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

Common Mistakes:

• Using this.setState in functional components
• Calling non-existent functions like updateState
• Trying to mutate state directly

3. Consider this React component snippet:

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

useEffect(() => {
  console.log('Count changed:', count);
}, [count]);

setCount(1);
setCount(2);

What will be logged to the console after these updates?

medium

A. Count changed: 1Count changed: 2

B. No output

C. Count changed: 2

D. Count changed: 0Count changed: 1Count changed: 2

Solution

1. Step 1: Understand state updates batching

   Multiple state updates in the same event batch are combined; only the last update triggers effect.

2. Step 2: Analyze useEffect dependency

   useEffect runs after render when count changes, so it logs only once with the final value 2.

3. Final Answer:

   Count changed: 2 -> Option C

4. Quick Check:

   State updates batch; effect logs last value [OK]

Hint: Multiple state updates batch; effect runs once with last value [OK]

Common Mistakes:

• Assuming useEffect runs after every setCount call immediately
• Expecting console to log intermediate values
• Not knowing React batches state updates

4. What is wrong with this React code snippet during the updating phase?

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

function increment() {
  count = count + 1;
  setCount(count);
}

medium

A. Directly modifying state variable instead of using setter

B. Missing dependency array in useEffect

C. Using setCount with a number instead of an object

D. Not returning JSX from the component

Solution

1. Step 1: Identify state mutation

   The code directly changes count variable, which is not allowed in React state management.

2. Step 2: Correct way to update state

   Use setCount(count + 1) without modifying count directly.

3. Final Answer:

   Directly modifying state variable instead of using setter -> Option A

4. Quick Check:

   Never mutate state variable directly; use setter [OK]

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

Common Mistakes:

• Trying to change state variable directly
• Confusing state variable with setter function
• Ignoring React's immutable state rule

5. You want to update a React component's state only when a prop value changes, avoiding unnecessary re-renders. Which approach correctly uses the updating phase to achieve this?

function MyComponent({ value }) {
  const [state, setState] = useState(value);

  // What should go here?
}

hard

A. useEffect(() => { setState(value); }, [value]);

B. useEffect(() => { setState(value); }, []);

C. setState(value); // directly in component body

D. useEffect(() => { setState(value); });

Solution

1. Step 1: Use useEffect to react to prop changes

   To update state only when value prop changes, use useEffect with [value] dependency.

2. Step 2: Avoid unnecessary updates

   Dependency array ensures effect runs only when value changes, preventing infinite loops or extra renders.

3. Final Answer:

   useEffect(() => { setState(value); }, [value]); -> Option A

4. Quick Check:

   useEffect with [value] updates state on prop change only [OK]

Hint: Use useEffect with dependency array for prop-based updates [OK]

Common Mistakes:

• Leaving dependency array empty causing no updates
• Calling setState directly in component body causing infinite loops
• Omitting dependency array causing effect on every render