What if you could write one line and get all possible string combinations without mistakes?
Why Template literal with unions in Typescript? - Purpose & Use Cases
Imagine you need to create many string combinations by hand, like greeting messages for different people and times of day, writing each possible sentence separately.
This manual way is slow and tiring. You might forget some combinations or make typos. Changing one part means rewriting many lines, which wastes time and causes errors.
Using template literals with unions lets you define parts of strings as sets of options and combine them automatically. This way, TypeScript helps create all valid combinations without writing each one manually.
type Greeting = 'Hello John' | 'Hello Jane' | 'Good morning John' | 'Good morning Jane';
type Time = 'Hello' | 'Good morning'; type Name = 'John' | 'Jane'; type Greeting = `${Time} ${Name}`;
This lets you easily build many string variations safely and quickly, making your code cleaner and less error-prone.
Think of a website showing personalized greetings based on user name and time of day. Template literal unions generate all valid greetings automatically.
Manual string combinations are slow and error-prone.
Template literal unions create all valid string combos automatically.
This makes code easier to write, read, and maintain.
Practice
Which of the following best describes a template literal with unions in TypeScript?
Solution
Step 1: Understand template literals and unions
Template literals allow embedding expressions in strings. Union types restrict values to a set of options.Step 2: Combine both concepts
Template literal with unions creates strings with fixed parts and limited variable parts, improving type safety.Final Answer:
A way to create specific string patterns by combining fixed text and union types. -> Option BQuick Check:
Template literal + union = specific string patterns [OK]
- Confusing unions with simple string concatenation
- Ignoring type safety benefits
- Thinking it's only about functions
Which of the following TypeScript declarations correctly uses a template literal with unions?
type Size = "small" | "medium" | "large";
type Message = `Size is ${Size}`;Solution
Step 1: Check the union type used inside template literal
The union typeSizeis "small" | "medium" | "large" and should be used inside the template literal.Step 2: Match the template literal syntax
The correct syntax is`Size is ${Size}`to restrict the string to those sizes.Final Answer:
type Message = `Size is ${Size}`; -> Option DQuick Check:
Use union type inside template literal exactly [OK]
- Replacing union with general types like string or number
- Using incorrect syntax for template literals
- Forgetting backticks around the template
What is the type of result in the following code?
type Color = "red" | "green" | "blue";
type Alert = `Alert: ${Color}`;
const result: Alert = "Alert: green";Solution
Step 1: Understand the template literal with union
The typeAlertcreates strings by combining "Alert: " with each value inColor.Step 2: Expand the union to all possible strings
SoAlertis the union of "Alert: red", "Alert: green", and "Alert: blue".Final Answer:
"Alert: red" | "Alert: green" | "Alert: blue" -> Option AQuick Check:
Template literal expands union to all combined strings [OK]
- Assuming only one string value is allowed
- Confusing union with single string
- Using general string type instead of union
Identify the error in this TypeScript code using template literals with unions:
type Status = "success" | "error";
type Message = `Status: ${string}`;
const msg: Message = "Status: success";Solution
Step 1: Check the template literal type definition
The template literal uses${string}which allows any string, not restricted toStatus.Step 2: Identify the correct usage
It should use${Status}to restrict values to "success" or "error" only.Final Answer:
Usingstringinside template literal instead of union typeStatus. -> Option AQuick Check:
Use union type inside template literal for safety [OK]
- Using
stringinstead of union type inside template - Ignoring type safety benefits
- Confusing string literals with template literals
Given the following types, which of these assignments is valid without TypeScript errors?
type Direction = "up" | "down";
type Action = "move" | "stop";
type Command = `${Action}-${Direction}`;
const cmd1: Command = "move-up";
const cmd2: Command = "stop-left";
const cmd3: Command = "move-down";
const cmd4: Command = "jump-up";Solution
Step 1: Understand the
CommandtypeCommandis a template literal combiningActionandDirectionwith a dash, so valid strings are "move-up", "move-down", "stop-up", "stop-down".Step 2: Check each assignment
cmd1= "move-up" (valid),cmd2= "stop-left" (invalid, "left" not in Direction),cmd3= "move-down" (valid),cmd4= "jump-up" (invalid, "jump" not in Action).Final Answer:
Only cmd1 and cmd3 are valid. -> Option CQuick Check:
Match both parts to union values exactly [OK]
- Assuming any string with dash is valid
- Ignoring union type restrictions
- Confusing Action and Direction values
Ready to prove it?
Pass the test and this pattern moves unknown
