What you will learn
- Explain the purpose, important state, and technical decisions behind Unions and Narrowing before implementing it.
- Produce or inspect an annotated concept model and state/evidence trace for Unions and Narrowing.
- Verify the result with the module-specific command, output, test, rendered state, query result, log, or measurement that proves the exercise worked.
What you need
- Open a small local project or disposable lab environment.
- Confirm the runtime, toolchain, or service needed for the module.
- Prepare one valid input and one invalid or boundary input.
Build the mental model
Unions and Narrowing focuses on this learner need: Use TypeScript to express expected data shapes and narrow unions safely so invalid states are caught before runtime while emitted JavaScript behavior remains understood. Use TypeScript source types, inference, unions, narrowing, interfaces, generics, compiler diagnostics, emitted JavaScript, and project configuration.
Track the changing state and identify the evidence that makes that state observable.
Identify the parts and boundaries
In Unions and Narrowing, static type checking versus runtime values. Union types and discriminants. Use TypeScript source types, inference, unions, narrowing, interfaces, generics, compiler diagnostics, emitted JavaScript, and project configuration.
- 1
Static type checking versus runtime values.
- 2
Union types and discriminants.
- 3
Control-flow narrowing.
- 4
Unknown versus any and safe parsing boundaries.
Trace one concrete case
Choose one realistic input for Unions and Narrowing and trace it using this path lens: Use TypeScript source types, inference, unions, narrowing, interfaces, generics, compiler diagnostics, emitted JavaScript, and project configuration. Predict the result before running the example, then compare prediction with evidence.
If the prediction fails, identify the assumption before changing the implementation.
UNIONS AND NARROWING
====================
1. Static type checking versus runtime values.
2. Union types and discriminants.
3. Control-flow narrowing.
4. Unknown versus any and safe parsing boundaries.
Evidence: the module-specific command, output, test, rendered state, query result, log, or measurement that proves the exercise worked
Read the concept map, predict one concrete result, then compare that prediction with the module example or native tool.A module-specific concept trace connecting core decisions to observable evidence.
practice/\n├── README.md\n├── unions-and-narrowing-concept-map.txt\n└── evidence/\n └── expected-result.txtApply Unions and Narrowing
Explain the purpose, important state, and technical decisions behind Unions and Narrowing before implementing it.
- Use the lesson-specific technical example as a reference, not a copy.
- Change one condition that matters to Unions and Narrowing.
- Verify the result with the module-specific command, output, test, rendered state, query result, log, or measurement that proves the exercise worked.
Compare a nearby alternative
For Unions and Narrowing, compare the shown mechanism with a nearby alternative. Use this technical point—Control-flow narrowing.—inside this path context: Use TypeScript source types, inference, unions, narrowing, interfaces, generics, compiler diagnostics, emitted JavaScript, and project configuration.
State the tradeoff in your own words.
Explain it back with evidence
Summarize Unions and Narrowing without reading the example. Explain the input or state, operation or decision, and result through this implementation lens: Use TypeScript source types, inference, unions, narrowing, interfaces, generics, compiler diagnostics, emitted JavaScript, and project configuration.
For Unions and Narrowing, use this evidence standard: the module-specific command, output, test, rendered state, query result, log, or measurement that proves the exercise worked. Interpret the evidence through this path context: Use TypeScript source types, inference, unions, narrowing, interfaces, generics, compiler diagnostics, emitted JavaScript, and project configuration.
Practice Unions and Narrowing
Create a one-page explanation of Unions and Narrowing using one diagram or state trace, one concrete example, and one observation that proves the model.
- 1
Write the expected result before starting.
- 2
Create a one-page explanation of Unions and Narrowing using one diagram or state trace, one concrete example, and one observation that proves the model.
- 3
Record the module-specific command, output, test, rendered state, query result, log, or measurement that proves the exercise worked and explain whether it matches the expectation.
Practice what you learned
Exercises are optional for lesson completion and contribute to a separate Practice Mastery score.
Core Check: Unions and Narrowing: Core Concepts for TypeScript Fundamentals
Complete a focused exercise for “Unions and Narrowing: Core Concepts for TypeScript Fundamentals”. Your task is to Use TypeScript to express expected data shapes and narrow unions safely so invalid states are caught before runtime while emitted JavaScript behavior remains understood. Use one concrete example and show evidence that the result is correct.
Verification target: a working unions and narrowing exercise with a documented technical result
This exercise has been updated since your saved draft. Your draft was kept. Reset only if you want the latest starter code.
Not completed
Start with Static type checking versus runtime values.. Then connect it to the lesson task: Use TypeScript to express expected data shapes and narrow unions safely so invalid states are caught before runtime while emitted JavaScript behavior remains understood.
Goal: Use TypeScript to express expected data shapes and narrow unions safely so invalid states are caught before runtime while emitted JavaScript behavior remains understood.
Concept: Static type checking versus runtime values.
Supporting idea: Union types and discriminants.
Expected result: a working unions and narrowing exercise with a documented technical result
Verification evidence: an annotated concept model and state/evidence trace for Unions and NarrowingThis reference answer connects the lesson task and technical concepts to observable evidence. Compare the structure and reasoning, not only the exact wording.
Mini Challenge: Unions and Narrowing: Core Concepts for TypeScript Fundamentals
Extend “Unions and Narrowing: Core Concepts for TypeScript Fundamentals” into a boundary or failure scenario. Start from this lesson task: Use TypeScript to express expected data shapes and narrow unions safely so invalid states are caught before runtime while emitted JavaScript behavior remains understood. Change one condition that matters, predict the outcome first, then show evidence that confirms or disproves the prediction.
Verification target: a working unions and narrowing exercise with a documented technical result
This exercise has been updated since your saved draft. Your draft was kept. Reset only if you want the latest starter code.
Not completed
Combine Static type checking versus runtime values. with Union types and discriminants.. Aim to produce: a working unions and narrowing exercise with a documented technical result.
Goal: Use TypeScript to express expected data shapes and narrow unions safely so invalid states are caught before runtime while emitted JavaScript behavior remains understood.
Predicted result: a working unions and narrowing exercise with a documented technical result
Approach:
1. Static type checking versus runtime values.
2. Union types and discriminants.
3. Change one boundary or failure condition.
4. Verify with observable evidence.
Evidence: an annotated concept model and state/evidence trace for Unions and NarrowingThis reference answer connects the lesson task and technical concepts to observable evidence. Compare the structure and reasoning, not only the exact wording.
Common mistakes to avoid
- Using any removes useful checking.
- Type assertion used instead of validation.
- Union not narrowed before property access.
- Assuming TypeScript validates runtime JSON.
Key takeaways
- Explain the purpose, important state, and technical decisions behind Unions and Narrowing before implementing it.
- Keep the exercise small enough to explain the important state and decision.
- Use the module-specific command, output, test, rendered state, query result, log, or measurement that proves the exercise worked rather than successful command completion alone.
Frequently asked questions
What should I be able to do before moving on?
You should be able to explain the purpose of Unions and Narrowing, build a small example without copying the lesson line by line, and diagnose a basic failure using the relevant tool or error output.
How much should I build for practice?
Keep the exercise small enough that you can explain every important input, state change, and output. Add complexity only after the core behavior is reliable.
Sources and further reading
- NarrowingTypeScript
- TypeScript HandbookTypeScript
- TypeScript TSConfig ReferenceTypeScript
Ready to continue?
Mark the lesson complete so your Learning Path progress stays current on this device.