Default props in React - Step-by-Step Execution

Concept Flow - Default props

Component Called

↓

Check Props Passed?

Yes No↓

Use Passed Props

↓

Render Component

When a React component is called, it checks if props are passed. If not, it uses default props before rendering.

Execution Sample

React

function Greeting({ name = "Guest" }) {
  return <h1>Hello, {name}!</h1>;
}

<Greeting />
<Greeting name="Alice" />

This code shows a Greeting component using a default prop for name if none is provided.

Execution Table

Step	Component Call	Props Passed	Name Value Used	Rendered Output
1	<Greeting />	No	"Guest"	<h1>Hello, Guest!</h1>
2	<Greeting name="Alice" />	Yes (name="Alice")	"Alice"	<h1>Hello, Alice!</h1>

💡 All component calls processed; default props used when no props passed.

Variable Tracker

Variable	Start	After Call 1	After Call 2	Final
name	undefined	"Guest"	"Alice"	"Alice"

Key Moments - 2 Insights

Why does the component show "Guest" when no name prop is passed?

Because the default value "Guest" is used when the name prop is undefined, as shown in execution_table step 1.

What happens if a name prop is passed?

The passed name prop overrides the default, as seen in execution_table step 2 where "Alice" is used.

Visual Quiz - 3 Questions

Look at the execution table, what is the name value used at step 1?

A undefined

B "Alice"

C "Guest"

D null

💡 Hint

Check the 'Name Value Used' column in execution_table row 1.

At which step does the component use the passed prop instead of the default?

A Step 2

B Step 1

C Both steps

D Neither step

💡 Hint

Look at the 'Props Passed' column in execution_table.

If we remove the default value from the component, what happens when <Greeting /> is called?

A It renders "Hello, Guest!"

B It renders "Hello, undefined!"

C It throws an error

D It renders nothing

💡 Hint

Refer to variable_tracker and how 'name' is set when no default is provided.

Concept Snapshot

Default props in React let components use fallback values when no props are passed.
Use function parameter defaults like ({ name = "Guest" }) to set them.
If a prop is passed, it overrides the default.
This ensures components always have values to render.
No need for separate defaultProps with modern React.

Full Transcript

This visual shows how React components use default props. When the Greeting component is called without a name prop, it uses the default "Guest". When called with name="Alice", it uses "Alice". The execution table tracks each call, showing the name value used and the rendered output. The variable tracker follows the name variable's value changes. Key moments clarify why defaults are used and how passed props override them. The quiz tests understanding of these steps. Default props help components render correctly even if some props are missing.

Practice

1. What is the main purpose of default props in a React functional component?

easy

A. To enforce type checking on props

B. To optimize component rendering speed

C. To make the component stateful

D. To provide fallback values for props that are not passed

Solution

1. Step 1: Understand what props are

   Props are inputs to React components that can be passed from parent components.

2. Step 2: Identify the role of default props

   Default props provide fallback values when no value is passed for a prop, preventing undefined values.

3. Final Answer:

   To provide fallback values for props that are not passed -> Option D

4. Quick Check:

   Default props = fallback values [OK]

Hint: Default props fill in missing props automatically [OK]

Common Mistakes:

• Confusing default props with state
• Thinking default props enforce types
• Assuming default props improve performance

2. Which of the following is the correct way to set default props in a React functional component using ES6 syntax?

easy

A. function MyComponent(props = { name: 'Guest' }) { return {props.name}; }

B. function MyComponent({ name = 'Guest' }) { return {name}; }

C. MyComponent.defaultProps = { name: 'Guest' }; function MyComponent(props) { return {props.name}; }

D. function MyComponent(props) { props.name = props.name || 'Guest'; return {props.name}; }

Solution

1. Step 1: Review ES6 default parameter syntax

   Default values can be set directly in the function parameter list using destructuring with defaults.

2. Step 2: Check each option

   function MyComponent({ name = 'Guest' }) { return <div>{name}</div>; } correctly uses destructuring with a default value: { name = 'Guest' }.

3. Final Answer:

   function MyComponent({ name = 'Guest' }) { return <div>{name}</div>; } -> Option B

4. Quick Check:

   Default props in parameters = function MyComponent({ name = 'Guest' }) { return <div>{name}</div>; } [OK]

Hint: Use destructuring with default values in parameters [OK]

Common Mistakes:

• Trying to set default props inside the function body
• Using defaultProps with functional components incorrectly
• Assigning default props to the whole props object

3. What will be rendered by this component?

function Greeting({ name = 'Friend' }) {
  return <h1>Hello, {name}!

medium

A. <h1>Hello, Friend!</h1>

B. <h1>Hello, undefined!</h1>

C. Error: Missing required prop 'name'

D. <h1>Hello, !</h1>

Solution

1. Step 1: Check the default prop value

   The component uses destructuring with a default value: name = 'Friend'.

2. Step 2: Analyze the usage without passing name

   No prop is passed, so the default 'Friend' is used.

3. Final Answer:

   <h1>Hello, Friend!</h1> -> Option A

4. Quick Check:

   Default prop used = 'Friend' [OK]

Hint: No prop passed? Default value is used [OK]

Common Mistakes:

• Assuming missing props cause errors
• Expecting undefined instead of default
• Confusing default props with required props

4. Identify the error in this component that tries to set default props:

function Button(props) {
  const { label } = props;
  return <button>{label}</button>;
}

Button.defaultProps = { label: 'Click me' };

// Usage:
<Button />

medium

A. defaultProps is not supported on functional components

B. The component should use destructuring with default values instead

C. No error; this code works correctly

D. The defaultProps assignment should be inside the function

Solution

1. Step 1: Understand defaultProps on functional components

   React supports defaultProps on functional components, so this syntax is valid.

2. Step 2: Check usage and output

   Since no label prop is passed, defaultProps provides 'Click me', so the button shows that text.

3. Final Answer:

   No error; this code works correctly -> Option C

4. Quick Check:

   defaultProps works on functions = No error; this code works correctly [OK]

Hint: defaultProps still works on functions but prefer defaults in parameters [OK]

Common Mistakes:

• Thinking defaultProps is deprecated for functional components
• Placing defaultProps inside the function body
• Confusing defaultProps with state initialization

5. You want a component to have a default prop that is an object with nested values. Which approach correctly sets default props to avoid errors if the prop is missing?

function Profile({ user = { name: 'Guest', age: 0 } }) {
  return <div>Name: {user.name}, Age: {user.age}</div>;
}

hard

A. Use destructuring with a default object in the parameter as shown

B. Set defaultProps = { user: { name: 'Guest', age: 0 } } after the function

C. Initialize user inside the function body with if (!user) user = {...}

D. Pass user as a required prop and do not set defaults

Solution

1. Step 1: Understand default props for nested objects

   Setting default nested objects in parameters prevents errors when accessing properties.

2. Step 2: Compare approaches

   Use destructuring with a default object in the parameter as shown uses destructuring with a default object, which safely provides nested defaults.

3. Final Answer:

   Use destructuring with a default object in the parameter as shown -> Option A

4. Quick Check:

   Default nested object in parameters = Use destructuring with a default object in the parameter as shown [OK]

Hint: Set nested defaults in parameter destructuring to avoid undefined errors [OK]

Common Mistakes:

• Setting defaultProps with nested objects can cause shallow merge issues
• Initializing defaults inside function body can be verbose and error-prone
• Not providing defaults leads to runtime errors accessing nested props