JavaScript in JSX with curly braces in code
return <p>{count * 2}</p>;
<img src={url} alt="" />; // not src="url"Read the example from data and control flow to the resulting UI. Keep the component boundary small.
Back to week 1
Topic
JavaScript in JSX with curly braces
Definition
JSX braces evaluate JavaScript expressions and insert their resulting values into an element tree.
In simpler words
Use { } for dynamic values and calculations inside markup.
Expressions vs statements, dynamic attributes, and nullish fallbacks.
After this you can
- Embed variables and expressions safely in JSX.
- Explain the trade-off to a teammate using a small example.
- Name at least one common bug pattern for this topic.
Understand JavaScript in JSX with curly braces
Expressions vs statements, dynamic attributes, and nullish fallbacks.
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 JavaScript in JSX with curly braces
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: Quotes instead of braces for variables
// Wrong
<img src="avatarUrl" />
// Right
<img src={avatarUrl} />Quotes make a literal string named avatarUrl.
Mistake: Statements as JSX children
// Wrong
return <div>{if (ok) return <p>Hi</p>}</div>;
// Right
return <div>{ok ? <p>Hi</p> : null}</div>;Only expressions are allowed inside { }.
Mistake: Rendering a raw object
// Wrong
return <pre>{user}</pre>;
// Right
return <pre>{user.name}</pre>;
// or JSON.stringify(user)React cannot render plain objects as children.
Live playground
JavaScript in JSX with curly braces sandbox
Change one input at a time and predict the next render.
Inside JSX, { expression } runs JavaScript. Quotes make a literal string.
Hello, Ada — double is 6
Wrong would be: src="name" (literal text), not src={name}
return <p>Hello, {name} — double is {count * 2}</p>;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