Avoiding prop drilling in React - Step-by-Step Execution

Concept Flow - Avoiding prop drilling

Parent Component

↓

Pass props down

↓

Child Component

↓

Pass props down

↓

Grandchild Component

↓

Parent Component

↓

Context Provider

↓

Any Nested Component

Prop drilling is when data is passed through many layers of components. Using React Context lets nested components get data directly, avoiding this.

Execution Sample

React

const ThemeContext = React.createContext('light');

function Parent() {
  return <ThemeContext.Provider value="dark">
    <Child />
  </ThemeContext.Provider>;
}

function Child() {
  return <Grandchild />;
}

function Grandchild() {
  const theme = React.useContext(ThemeContext);
  return <div>Theme is {theme}</div>;
}

This code shows a parent providing a theme value via context, and a grandchild reading it directly without props.

Execution Table

Step	Component	Action	Props Passed	Context Used	Rendered Output
1	Parent	Render Parent with ThemeContext.Provider value='dark'	None	Provides 'dark'	<Child /> rendered
2	Child	Render Child	No props passed	No context used	<Grandchild /> rendered
3	Grandchild	Render Grandchild	No props passed	Reads 'dark' from ThemeContext	<div>Theme is dark</div>
4	Exit	Rendering complete	No further props	Context value used by Grandchild	Final output displayed

💡 Rendering stops after Grandchild uses context to display theme without prop drilling.

Variable Tracker

Variable	Parent Render	Child Render	Grandchild Render	Final
props	null	null	null	null
ThemeContext value	dark (provided)	dark (available)	dark (used)	dark
Rendered Output	Child component	Grandchild component	<div>Theme is dark</div>	<div>Theme is dark</div>

Key Moments - 3 Insights

Why doesn't the Child component receive any props?

Because the theme value is provided via Context, Child doesn't need to pass props down, as shown in execution_table step 2.

How does Grandchild get the theme value without props?

Grandchild uses React.useContext to read the value directly from ThemeContext, avoiding prop drilling (execution_table step 3).

What problem does Context solve here?

It avoids passing props through intermediate components that don't use them, simplifying data flow (see concept_flow diagram).

Visual Quiz - 3 Questions

Look at the execution_table, what is the ThemeContext value when Grandchild renders?

A undefined

B "dark"

C "light"

D null

💡 Hint

Check the 'Context Used' column at step 3 in execution_table.

At which step does the Child component render without receiving props?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Look at the 'Props Passed' column for Child in execution_table.

If we removed ThemeContext.Provider, what would Grandchild display?

A An error

B "Theme is dark"

C "Theme is light"

D "Theme is undefined"

💡 Hint

Default context value is 'light' as set in React.createContext('light').

Concept Snapshot

Avoid prop drilling by using React Context.
Create a Context with React.createContext(defaultValue).
Wrap components with Context.Provider to supply value.
Nested components use React.useContext to access value directly.
This skips passing props through many layers.
Simplifies data flow and component structure.

Full Transcript

Prop drilling happens when you pass data through many components that don't need it, just to reach a nested one. React Context helps by letting you put data in a special place (Context Provider) at a high level. Then any nested component can grab that data directly using useContext. This means you don't have to pass props down step-by-step. In the example, Parent provides a theme value 'dark' via ThemeContext.Provider. Child doesn't get or pass any props. Grandchild uses useContext to read 'dark' and shows it. This avoids prop drilling and keeps code cleaner.

Practice

1. What is the main problem that prop drilling causes in React applications?

easy

A. Not using hooks properly in functional components

B. Using too many state variables in a single component

C. Rendering components multiple times unnecessarily

D. Passing props through many layers even if intermediate components don't need them

Solution

1. Step 1: Understand what prop drilling means

   Prop drilling happens when props are passed down through many components that don't use them, just to reach a deeply nested component.

2. Step 2: Identify the main issue caused by prop drilling

   This makes the code harder to maintain and understand because many components receive props they don't need.

3. Final Answer:

   Passing props through many layers even if intermediate components don't need them -> Option D

4. Quick Check:

   Prop drilling = Passing props through many layers [OK]

Hint: Prop drilling means unnecessary passing props down layers [OK]

Common Mistakes:

• Confusing prop drilling with state management issues
• Thinking prop drilling is about rendering performance
• Believing prop drilling is caused by hooks misuse

2. Which of the following is the correct way to create a React Context to avoid prop drilling?

easy

A. const MyContext = React.useContext();

B. const MyContext = React.createContext();

C. const MyContext = React.useState();

D. const MyContext = React.useEffect();

Solution

1. Step 1: Recall the React API for creating context

   React provides createContext to create a context object for sharing data.

2. Step 2: Identify the correct syntax

   The correct syntax is const MyContext = React.createContext();. The other options are hooks used for different purposes.

3. Final Answer:

   const MyContext = React.createContext(); -> Option B

4. Quick Check:

   createContext() creates context [OK]

Hint: Use createContext() to make a context object [OK]

Common Mistakes:

• Using useContext() to create context instead of consume it
• Confusing useState() or useEffect() with context creation
• Missing parentheses after createContext

3. Given this code snippet, what will be the output inside Child component?

const MyContext = React.createContext('default');

function Parent() {
  return (
    
      
    
  );
}

function Child() {
  const value = React.useContext(MyContext);
  return <div>{value}</div>;
}

medium

A. <div>hello</div>

B. <div>default</div>

C. <div>undefined</div>

D. Error: useContext must be inside a Provider

Solution

1. Step 1: Understand the context default and provider value

   The context default is 'default', but the Parent component provides the value 'hello' via MyContext.Provider.

2. Step 2: Determine what useContext returns inside Child

   The Child component uses useContext(MyContext), so it receives the nearest provider's value, which is 'hello'.

3. Final Answer:

   <div>hello</div> -> Option A

4. Quick Check:

   useContext returns nearest Provider value [OK]

Hint: useContext gets nearest Provider value, not default [OK]

Common Mistakes:

• Assuming default value is always used
• Thinking useContext returns undefined without explicit value
• Confusing Provider value with component props

4. Identify the error in this code that tries to avoid prop drilling using React Context:

const MyContext = React.createContext();

function Parent() {
  const value = 'data';
  return <Child />;
}

function Child() {
  const value = React.useContext(MyContext);
  return <div>{value}</div>;
}

medium

A. MyContext.Provider is missing around Child component

B. useContext is used incorrectly inside Child

C. createContext must have a default value

D. Parent should pass value as a prop to Child

Solution

1. Step 1: Check if Provider wraps components needing context

   The Parent component returns <Child /> without wrapping it in MyContext.Provider.

2. Step 2: Understand useContext requires Provider to get value

   Without a Provider, useContext(MyContext) returns the default value, which is undefined here, likely not intended.

3. Final Answer:

   MyContext.Provider is missing around Child component -> Option A

4. Quick Check:

   Provider missing = context value undefined [OK]

Hint: Always wrap consumers with Provider to supply context [OK]

Common Mistakes:

• Thinking createContext must have default value
• Believing useContext works without Provider
• Confusing prop passing with context usage

5. You have a deeply nested component tree where ThemeContext provides a theme string. You want to avoid prop drilling and also allow components to update the theme. Which approach correctly combines context and state to achieve this?

hard

A. Use multiple contexts for theme and setTheme separately and pass them as props

B. Pass theme as a prop from top to bottom and use useState only in the deepest component

C. Create ThemeContext with createContext, provide {theme, setTheme} from a state in a top-level component, and consume both in nested components

D. Store theme in a global variable and read it directly in nested components

Solution

1. Step 1: Understand how to share state and updater via context

   To avoid prop drilling and allow updates, the context should provide both the current value and a function to update it.

2. Step 2: Use createContext and provide state and setter from top-level

   Create a context with createContext(), then in a top-level component use useState to hold theme and pass both theme and setTheme in the Provider's value.

3. Step 3: Consume both theme and setTheme in nested components

   Nested components use useContext to get both and can read or update the theme without prop drilling.

4. Final Answer:

   Create ThemeContext with createContext, provide {theme, setTheme} from a state in a top-level component, and consume both in nested components -> Option C

5. Quick Check:

   Context with state and setter avoids prop drilling [OK]

Hint: Provide state and setter in context value to update data [OK]

Common Mistakes:

• Passing only value without setter in context
• Using global variables instead of React state
• Passing props through many layers instead of context