Updating phase in React

Introduction

The updating phase in React happens when a component changes its data or properties. It helps the app show the latest information on the screen.

When a user types in a form and the app needs to show what they typed.

When new data arrives from the internet and the app updates the display.

When a button click changes what is shown on the page.

When a timer or clock updates every second.

When a parent component sends new information to a child component.

Syntax

React

import React, { useState, useEffect } from 'react';

function ComponentName(props) {
  const [state, setState] = useState(initialValue);

  useEffect(() => {
    // code to run after update
  }, [state, props]);

  return (
    <div>{state}</div>
  );
}

The updating phase happens when state or props change.

The useEffect hook can run code after updates when dependencies change.

Examples

Updates the count state when the button is clicked, causing the component to re-render.

React

import React, { useState } from 'react';

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

  return (
    <button onClick={() => setCount(count + 1)}>
      Clicked {count} times
    </button>
  );
}

This runs after the count state updates, logging the new value.

React

import React, { useEffect } from 'react';

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

  return null;
}

Sample Program

This component updates the displayed text as the user types. The useEffect logs each update to the console.

React

import React, { useState, useEffect } from 'react';

export default function UpdatingPhaseExample() {
  const [text, setText] = useState('Hello');

  useEffect(() => {
    console.log('Text updated to:', text);
  }, [text]);

  return (
    <div>
      <input
        aria-label="Input text"
        value={text}
        onChange={e => setText(e.target.value)}
        placeholder="Type something"
      />
      <p>You typed: {text}</p>
    </div>
  );
}

Important Notes

Updating happens automatically when state or props change.

Too many updates can slow the app, so update only when needed.

Use useEffect to run code after updates, like fetching data or logging.

Summary

The updating phase shows new data on the screen when state or props change.

Use useState to hold data and useEffect to react to changes.

Updating keeps your app interactive and fresh for users.

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