What if your program could instantly know exactly what value it's dealing with, avoiding hidden bugs?
Why Literal types and value narrowing in Typescript? - Purpose & Use Cases
Imagine you have a program that accepts user commands like 'start', 'stop', or 'pause'. Without special checks, you might accidentally allow typos or unexpected values, causing bugs or crashes.
Manually checking every possible string or value is slow and error-prone. You might forget a case or mistype a check, leading to unexpected behavior that's hard to find and fix.
Literal types let you specify exact allowed values, and value narrowing helps the program understand which exact value it's working with. This prevents mistakes and makes your code safer and clearer.
function handleCommand(cmd: string) {
if (cmd === 'start' || cmd === 'stop' || cmd === 'pause') {
// do something
}
}type Command = 'start' | 'stop' | 'pause'; function handleCommand(cmd: Command) { if (cmd === 'start') { // do start } else if (cmd === 'stop') { // do stop } else if (cmd === 'pause') { // do pause } }
You can write code that knows exactly what values are allowed and safely handle each case without guesswork or errors.
Think of a traffic light system where the light can only be 'red', 'yellow', or 'green'. Literal types ensure you never accidentally use an invalid color, keeping the system reliable.
Literal types specify exact allowed values.
Value narrowing helps the program understand which value it has.
This combination makes code safer and easier to maintain.
Practice
Solution
Step 1: Understand the purpose of literal types
Literal types let you restrict a variable to exact values like 'yes' or 10 instead of general types like string or number.Step 2: Compare options with the definition
Only Specify exact allowed values for a variable correctly describes this feature; others describe unrelated concepts.Final Answer:
Specify exact allowed values for a variable -> Option AQuick Check:
Literal types = exact allowed values [OK]
- Confusing literal types with classes
- Thinking literal types disable type checking
- Assuming literal types allow any value
Solution
Step 1: Check the syntax for literal type declaration
To declare a variable with a literal type, you specify the exact value in quotes as the type, like 'open'.Step 2: Evaluate each option
let status: 'open' = 'open'; correctly declares status with type 'open' and assigns 'open'. let status: string = 'open'; uses string type, not literal. let status = 'open'; infers string type but not literal. let status: 'open'; status = 'closed'; declares type 'open' but assigns 'closed', which is invalid.Final Answer:
let status: 'open' = 'open'; -> Option CQuick Check:
Literal type syntax uses exact value in quotes [OK]
- Assigning a different value than the literal type
- Using general types instead of literal types
- Omitting the type and expecting literal type
type Direction = 'left' | 'right';
function move(dir: Direction) {
if (dir === 'left') {
return 'Moving left';
} else {
return 'Moving right';
}
}
console.log(move('right'));Solution
Step 1: Understand the function behavior with literal type
The function move accepts only 'left' or 'right'. It returns 'Moving left' if input is 'left', else 'Moving right'.Step 2: Trace the function call with 'right'
Calling move('right') triggers the else branch, returning 'Moving right'.Final Answer:
Moving right -> Option AQuick Check:
Input 'right' returns 'Moving right' [OK]
- Confusing which branch runs for 'right'
- Expecting compile error for valid literal
- Ignoring else branch
type Status = 'success' | 'error';
function handle(status: Status) {
if (status === 'success') {
console.log('Success!');
} else if (status === 'fail') {
console.log('Failed!');
}
}Solution
Step 1: Check the allowed literal types for Status
Status can only be 'success' or 'error'.Step 2: Analyze the else if condition
The code checks if status === 'fail', which is not part of Status type, causing a type error.Final Answer:
The else if condition checks an invalid literal 'fail' -> Option DQuick Check:
Check conditions must match literal types [OK]
- Using literals not declared in the union type
- Ignoring TypeScript errors on invalid comparisons
- Assuming missing return type causes error here
result after the if statement?type Mode = 'auto' | 'manual';
function setMode(mode: Mode) {
let result: string | undefined;
if (mode === 'auto') {
result = 'Automatic mode set';
} else {
result = undefined;
}
return result;
}Solution
Step 1: Analyze variable declaration and assignments
Variable result is declared as string | undefined. Inside if, assigned string; else assigned undefined.Step 2: Determine narrowed type after if
Since result can be either string or undefined depending on mode, its type remains string | undefined.Final Answer:
string | undefined -> Option BQuick Check:
Variable type includes all assigned values [OK]
- Assuming type narrows to string only
- Ignoring undefined assignment
- Confusing Mode type with result type
Ready to prove it?
Pass the test and this pattern moves unknown
