Passing props to a component in code
<TicketRow title="Fix cookies" status="open" />Read the example from data and control flow to the resulting UI. Keep the component boundary small.
Back to week 1
Topic
Passing props to a component
Definition
Props are read-only inputs supplied by a parent component to a child component.
In simpler words
Props are component function arguments from the parent.
One-way data flow, prop naming, and children.
After this you can
- Pass data down and keep ownership clear.
- Explain the trade-off to a teammate using a small example.
- Name at least one common bug pattern for this topic.
Understand Passing props to a component
One-way data flow, prop naming, and children.
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.
Apply Passing props to a component
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: Mutating props
// Wrong
function Row(props) {
props.title = "x"; // no
return <span>{props.title}</span>;
}
// Right
function Row({ title, onRename }) {
return <button onClick={() => onRename("x")}>{title}</button>;
}Ask the parent to update; props are read-only.
Mistake: Prop name typo
// Wrong
<Hello namee="Ada" />
function Hello({ name }) { return <p>{name}</p>; }
// Right
<Hello name="Ada" />Typos fail silently — UI is blank.
Mistake: Endless prop drilling
// Wrong
<A user={u}><B user={u}><C user={u} /></B></A>
// Right
// Compose children, or use context for stable cross-cutting valuesPass only what each layer needs; avoid tunnels of unused props.
Live playground
Passing props to a component sandbox
Change one input at a time and predict the next render.
Ship Pulse — open
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