Why Context best practices in React? - Purpose & Use Cases

The Big Idea

Discover how to stop prop-drilling headaches and make your React code cleaner with Context best practices!

The Scenario

Imagine you have a React app where many components need to share the same data, like user info or theme settings. You try passing this data down through props from parent to child components, all the way through many layers.

The Problem

Passing props through many layers is tiring and error-prone. It makes your code messy and hard to maintain. If you want to change the shared data, you must update many components, which is slow and confusing.

The Solution

React Context lets you share data easily across many components without passing props manually. It creates a central place for data that any component can access, making your code cleaner and easier to update.

Before vs After

✗ Before

function App() {
  return <Parent user={user} />;
}
function Parent({ user }) {
  return <Child user={user} />;
}
function Child({ user }) {
  return <div>{user.name}</div>;
}

✓ After

const UserContext = React.createContext();
function App() {
  return <UserContext.Provider value={user}>
    <Child />
  </UserContext.Provider>;
}
function Child() {
  const user = React.useContext(UserContext);
  return <div>{user.name}</div>;
}

What It Enables

It enables easy, clean sharing of data across many components without messy prop passing.

Real Life Example

Think of a website where the user's login status and preferences are needed in many places like the header, sidebar, and profile page. Context makes sharing this info simple and consistent.

Key Takeaways

Passing props deeply is hard and messy.

Context provides a clean way to share data globally.

Using Context best practices keeps your React app organized and easy to maintain.

Practice

1. What is the main purpose of React Context?

easy

A. To handle routing between pages

B. To style components globally

C. To manage component local state only

D. To share data between components without passing props manually

Solution

1. Step 1: Understand React Context role

   React Context allows sharing data across many components without passing props at every level.

2. Step 2: Compare with other options

   Styling, local state, and routing are handled by other React features or libraries, not Context.

3. Final Answer:

   To share data between components without passing props manually -> Option D

4. Quick Check:

   Context shares data without prop drilling [OK]

Hint: Context shares data without passing props repeatedly [OK]

Common Mistakes:

• Confusing Context with styling or routing
• Thinking Context manages only local state
• Assuming Context replaces all state management

2. Which of the following is the correct way to create a Context in React?

easy

A. const MyContext = new Context();

B. const MyContext = createContext();

C. const MyContext = React.createContext();

D. const MyContext = React.useContext();

Solution

1. Step 1: Recall Context creation syntax

   React Context is created using React.createContext() function.

2. Step 2: Check other options

   A uses invalid constructor, B misses React prefix, D calls a hook instead of creating context.

3. Final Answer:

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

4. Quick Check:

   Use React.createContext() to create context [OK]

Hint: Create context with React.createContext() [OK]

Common Mistakes:

• Omitting React prefix
• Using new keyword incorrectly
• Confusing useContext hook with createContext

3. Given this code snippet, what will be logged to the console?

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

function DisplayTheme() {
  const theme = React.useContext(ThemeContext);
  console.log(theme);
  return <div>Current theme: {theme}</div>;
}

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

medium

A. "dark"

B. "light"

C. undefined

D. Error: useContext called outside Provider

Solution

1. Step 1: Identify Provider value

   The ThemeContext.Provider wraps DisplayTheme with value "dark".

2. Step 2: Understand useContext behavior

   useContext reads the nearest Provider value, so theme is "dark" inside DisplayTheme.

3. Final Answer:

   "dark" -> Option A

4. Quick Check:

   useContext reads Provider value, not default [OK]

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

Common Mistakes:

• Assuming default value is used despite Provider
• Thinking useContext returns undefined without explicit value
• Confusing useContext with useState

4. What is wrong with this React Context usage?

const UserContext = React.createContext();

function Profile() {
  const user = React.useContext(UserContext);
  return <div>User: {user.name}</div>;
}

function App() {
  return <Profile />;
}

medium

A. UserContext.Provider is missing, so user is undefined causing error

B. useContext hook is used incorrectly inside Profile

C. React.createContext() requires a default value

D. Profile component should not access context directly

Solution

1. Step 1: Check for Provider wrapping

   App renders Profile without wrapping it in UserContext.Provider, so context value is undefined.

2. Step 2: Understand consequence in Profile

   Accessing user.name when user is undefined causes runtime error.

3. Final Answer:

   UserContext.Provider is missing, so user is undefined causing error -> Option A

4. Quick Check:

   Missing Provider means context value is undefined [OK]

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

Common Mistakes:

• Thinking createContext must have default value
• Believing useContext usage is incorrect here
• Assuming components can't access context directly

5. You want to update a theme value shared via Context from a nested component. Which is the best practice to enable this?

hard

A. Use useState inside the nested component to update theme locally

B. Pass a setter function in the Context value and call it inside the nested component

C. Create a new Context inside the nested component to override theme

D. Modify the Context object directly without Provider

Solution

1. Step 1: Understand Context update pattern

   To update shared data, pass a setter function (like from useState) in Context value.

2. Step 2: Evaluate other options

   Using local useState won't update shared theme; creating new Context breaks sharing; modifying Context object directly is invalid.

3. Final Answer:

   Pass a setter function in the Context value and call it inside the nested component -> Option B

4. Quick Check:

   Pass setter in Context to update shared state [OK]

Hint: Pass setter function via Context to update shared state [OK]

Common Mistakes:

• Trying to update Context value directly
• Using local state instead of shared state
• Creating multiple Contexts unnecessarily