Fullstack CourseLearn by building
Back to week 2

Topic

Passing data deeply with context

Definition

React Context lets a provider make a value available to descendant components without manually passing it through every intermediate prop.

In simpler words

Context is a shared channel for a subtree, useful when many levels need the same value.

createContext, providers, consumers, and focused context values.

After this you can

  • Avoid repetitive prop threading for stable cross-cutting data.
  • Explain the trade-off to a teammate using a small example.
  • Name at least one common bug pattern for this topic.

Understand Passing data deeply with context

createContext, providers, consumers, and focused context values.

Start by identifying which value or browser behavior changes. Then describe the UI from that current input instead of editing the DOM as a separate source of truth.

Passing data deeply with context in code

const ThemeContext = createContext("light");
<ThemeContext.Provider value="dark"><Page /></ThemeContext.Provider>;

Read the example from data and control flow to the resulting UI. Keep the component boundary small.

Apply Passing data deeply with context

Keep rendering as a calculation. Put user-triggered changes in event handlers, preserve UI memory in state, and reserve external synchronization for Effects or the server-state layer.

Name values by their UI meaning, test the loading and error path when data is remote, and avoid keeping two editable copies of the same value.

Ask before adding code: is this local UI memory, shared client state, or Nest-owned server state?

Where bugs hide

Definition

High-bug areas are places where a small API misuse looks correct but produces stale UI, duplicate work, or silent failures.

In simpler words

Each mistake below shows Wrong vs Right code — compare them side by side.

When something misbehaves, match the symptom to a pattern below before rewriting the feature.

Prefer fixing the ownership or update path over adding another Effect or sync step.

Mistake: Hot value in wide context

// Wrong
<AppContext.Provider value={{ tickets, draft, theme, user }}>

// Right
// Split contexts; keep frequently changing values narrow

Wide, hot providers re-render large trees.

Mistake: Nest lists in context instead of Query

// Wrong
const TicketsContext = createContext([])

// Right
useQuery({ queryKey: ["tickets"], queryFn: list })

Server cache belongs in Query.

Mistake: Missing Provider

// Wrong
const v = useContext(ThemeContext); // undefined in prod route

// Right
<ThemeContext.Provider value="dark">{children}</ThemeContext.Provider>

Wrap the subtree that consumes the context.

Live playground

Passing data deeply with context sandbox

Change one input at a time and predict the next render.

Deep child reads theme = light (no prop drilling)

Keep in mind

  • Keep the formal definition in mind; it explains which tool belongs where.
  • Prefer one source of truth over synchronized copies of the same value.
  • When behavior surprises you, trace: input → update → render → committed UI.
  • Study the Wrong vs Right examples in “Where bugs hide” before you merge.

Test

Check your understanding

At least 10 questions — mix of concept, syntax, practical, and logic. Score ≥ 80% (enforced by the API) to save progress.

Checking your session…

10 questions · concept 3 · syntax 3 · practical 2 · logic 2

Concept1. Which statement best defines Passing data deeply with context?
Syntax2. Which implementation matches Passing data deeply with context?
Practical3. When building a feature, when is Passing data deeply with context the right choice?
Logic4. What reasoning keeps Passing data deeply with context predictable as values change?
Concept5. Which statement best defines Passing data deeply with context?
Syntax6. Which implementation matches Passing data deeply with context?
Practical7. When building a feature, when is Passing data deeply with context the right choice?
Logic8. What reasoning keeps Passing data deeply with context predictable as values change?
Concept9. Which statement best defines Passing data deeply with context?
Syntax10. Which implementation matches Passing data deeply with context?