Why template literal types are powerful in Typescript - Challenge Your Understanding

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of Template Literal Type Combination

What is the type of Result after this code runs?

Typescript

type Colors = "red" | "blue";
type Shades = "light" | "dark";
type Result = `${Shades}-${Colors}`;

// What is Result?

A "light-red-dark-blue"

B "light" | "dark" | "red" | "blue"

C "light-red" | "light-blue" | "dark-red" | "dark-blue"

D "light-red" & "light-blue" & "dark-red" & "dark-blue"

💡 Hint

Think about how template literal types combine each option from both unions.

Template literal types create all combinations of the union members by concatenating them with the given pattern.

🧠 Conceptual

intermediate

Why Use Template Literal Types for String Manipulation?

Which of the following best explains why template literal types are powerful in TypeScript?

A They automatically convert strings to numbers for easier calculations.

B They allow creating new string literal types by combining existing ones, enabling precise type checks on dynamic strings.

C They let you write multi-line strings without escape characters.

D They replace all string types with a generic string type to simplify code.

💡 Hint

Think about how template literal types help with type safety for strings.

Template literal types let you build new string types from unions, so TypeScript can check if strings match expected patterns.

❓ Predict Output

advanced

Output of Nested Template Literal Types

What is the type of Combined after this code?

Typescript

type Prefix = "get" | "set";
type Entity = "User" | "Product";
type Combined = `${Prefix}${Entity}Info`;

// What is Combined?

A "getUserInfoProduct" | "setUserInfoProduct"

B "get" | "set" | "User" | "Product" | "Info"

C "getUser" | "setProduct" | "Info"

D "getUserInfo" | "getProductInfo" | "setUserInfo" | "setProductInfo"

💡 Hint

Consider how each prefix combines with each entity and the fixed suffix.

The template literal type creates all combinations of Prefix and Entity, then adds 'Info' at the end.

🔧 Debug

advanced

Identify the Error in Template Literal Type Usage

What error will this TypeScript code produce?

Typescript

type A = "foo" | "bar";
type B = `${A}`;

// Missing closing backtick

A SyntaxError: Unterminated template literal type

B TypeError: Cannot assign union to template literal

C No error, compiles fine

D ReferenceError: A is not defined

💡 Hint

Check the syntax carefully for missing characters.

The template literal type is missing the closing backtick, causing a syntax error.

🚀 Application

expert

Using Template Literal Types to Enforce API Endpoint Patterns

Given these types, which option correctly defines ApiEndpoint to represent endpoints like '/user/123' or '/product/456' where the number is dynamic but must be a string literal type?

Typescript

type Resource = "user" | "product";
type Id = `${number}`;

// Define ApiEndpoint here

A type ApiEndpoint = `/${Resource}/${Id}`;

B type ApiEndpoint = `/${Resource}/${number}`;

C type ApiEndpoint = `/${Resource}/number`;

D type ApiEndpoint = `/${Resource}/123` | `/${Resource}/456`;

💡 Hint

Use template literal types with string literal unions and template types for numbers.

Option A correctly uses a template literal type combining Resource and Id (which is a string literal of a number) to represent dynamic numeric IDs as strings.

Practice

1. What is the main benefit of using template literal types in TypeScript?

easy

A. They allow creating new string types by combining existing ones.

B. They execute string concatenation at runtime.

C. They replace all string types with numbers.

D. They disable type checking for strings.

Solution

1. Step 1: Understand template literal types purpose

   Template literal types combine string types to form new string types at compile time.

2. Step 2: Compare options with this purpose

   Only They allow creating new string types by combining existing ones. correctly describes this benefit; others describe runtime behavior or incorrect features.

3. Final Answer:

   They allow creating new string types by combining existing ones. -> Option A

4. Quick Check:

   Template literal types build new string types = A [OK]

Hint: Remember: template literal types create new string types, not runtime strings [OK]

Common Mistakes:

• Confusing template literal types with runtime string concatenation
• Thinking they disable type checking
• Assuming they convert strings to numbers

2. Which of the following is the correct syntax to define a template literal type combining 'hello' and a variable T?

easy

A. type Greet = hello${T};

B. type Greet = `hello + ${T}`;

C. type Greet = 'hello' + T;

D. type Greet = `hello${T}`;

Solution

1. Step 1: Recall template literal type syntax

   Template literal types use backticks with placeholders like ${T} inside, no plus signs.

2. Step 2: Check each option's syntax

   type Greet = `hello${T}`; correctly uses backticks and ${T} without extra symbols; others have syntax errors.

3. Final Answer:

   type Greet = `hello${T}`; -> Option D

4. Quick Check:

   Correct template literal syntax uses backticks and ${} = A [OK]

Hint: Use backticks and ${} for variables inside template literal types [OK]

Common Mistakes:

• Using plus signs inside template literal types
• Omitting backticks
• Not wrapping variable in ${}

3. What is the resulting type of this TypeScript code?

type Name = 'Alice' | 'Bob';
type Greeting = `Hello, ${Name}!`;

medium

A. `Hello!`

B. `Hello, Name!`

C. `Hello, Alice!` | `Hello, Bob!`

D. `Hello, ${Name}!`

Solution

1. Step 1: Understand union substitution in template literal types

   The union 'Alice' | 'Bob' substitutes into the template, creating a union of strings.

2. Step 2: Form the combined type

   Resulting type is `Hello, Alice!` | `Hello, Bob!`, combining each union member with the template.

3. Final Answer:

   `Hello, Alice!` | `Hello, Bob!` -> Option C

4. Quick Check:

   Union expands inside template literals = D [OK]

Hint: Union types inside template literals create unions of all combinations [OK]

Common Mistakes:

• Thinking the union stays as a single string with ${Name}
• Ignoring union expansion
• Confusing template literal type with runtime string

4. Identify the error in this TypeScript code using template literal types:

type Status = 'success' | 'error';
type Message = `Status: ${Status}`;

const msg: Message = 'Status: fail';

medium

A. Template literal types cannot use unions.

B. Assigning 'Status: fail' is invalid because 'fail' is not in Status union.

C. Backticks are missing around the string assignment.

D. The variable msg should be a number, not a string.

Solution

1. Step 1: Check allowed values for Message type

   Message type expands to 'Status: success' | 'Status: error' only.

2. Step 2: Validate assigned value

   Assigned string 'Status: fail' is not part of the allowed union, causing a type error.

3. Final Answer:

   Assigning 'Status: fail' is invalid because 'fail' is not in Status union. -> Option B

4. Quick Check:

   Assigned string must match template literal union = B [OK]

Hint: Check if assigned string matches all union members in template literal type [OK]

Common Mistakes:

• Assuming any string fits template literal type
• Thinking unions can't be used in template literals
• Ignoring type mismatch errors

5. Given these types:

type Event = 'click' | 'hover';
type Element = 'button' | 'link';
type EventName = `${Element}_${Event}`;

Which of the following is NOT assignable to a variable of type EventName?

hard

A. 'button_focus'

B. 'link_hover'

C. 'button_click'

D. 'link_click'

Solution

1. Step 1: Understand EventName type combinations

   EventName combines Element and Event with underscore, so valid values are 'button_click', 'button_hover', 'link_click', 'link_hover'.

2. Step 2: Identify invalid assignment

   'button_focus' is invalid because 'focus' is not in Event union.

3. Final Answer:

   'button_focus' -> Option A

4. Quick Check:

   Only combinations of Element and Event are valid = C [OK]

Hint: Check if both parts of template literal are in their unions [OK]

Common Mistakes:

• Assuming any string with underscore is valid
• Ignoring union members in template literal types
• Confusing runtime strings with type literals