Why Pattern matching with template literals in Typescript? - Purpose & Use Cases

The Big Idea

Discover how a simple pattern can replace complex string checks and save you hours of debugging!

The Scenario

Imagine you have a list of text messages and you want to find all messages that start with a specific word or phrase. Doing this by checking each message character by character or using complicated string functions can be confusing and slow.

The Problem

Manually checking patterns means writing lots of code to slice and compare parts of strings. It's easy to make mistakes, miss cases, or write code that's hard to read and maintain. This slows you down and causes bugs.

The Solution

Pattern matching with template literals lets you write clear, readable patterns that look like the text you want to find. It makes matching parts of strings simple and elegant, reducing errors and saving time.

Before vs After

✗ Before

if (message.startsWith('Hello') && message.endsWith('!')) { /* do something */ }

✓ After

if (message.match(/^Hello.*!$/)) { /* do something */ }

What It Enables

This lets you quickly and clearly find or extract parts of strings based on patterns, making text processing tasks much easier and more reliable.

Real Life Example

For example, filtering chat messages that start with a command like '/help' or '/start' becomes straightforward and easy to read using pattern matching with template literals.

Key Takeaways

Manual string checks are slow and error-prone.

Template literal pattern matching makes code clearer and simpler.

It helps you find and work with text patterns easily.

Practice

1. What does pattern matching with template literals in TypeScript primarily help you do?

easy

A. Create new variables dynamically

B. Automatically generate functions from strings

C. Change the type of a variable at runtime

D. Check if a string fits a specific shape or format

Solution

1. Step 1: Understand the purpose of pattern matching

   Pattern matching with template literals is used to verify if strings follow a certain pattern or format.

2. Step 2: Relate to template literals usage

   Template literals allow embedding expressions and patterns to check string shapes easily.

3. Final Answer:

   Check if a string fits a specific shape or format -> Option D

4. Quick Check:

   Pattern matching = Check string shape [OK]

Hint: Pattern matching checks string shapes, not variable types [OK]

Common Mistakes:

• Confusing pattern matching with variable creation
• Thinking it changes variable types
• Assuming it generates functions automatically

2. Which of the following is the correct syntax to use a template literal pattern in a TypeScript type check?

easy

A. type ID = `${string}-${number}`;

B. type ID = '${string}-${number}';

C. ;`}rebmun{$-}gnirts{$` = DI epyt

D. type ID = `${string}-${number}`

Solution

1. Step 1: Identify correct template literal syntax

   Template literals use backticks (`) and embed types inside ${} without quotes.

2. Step 2: Check for correct punctuation

   type ID = `${string}-${number}`; correctly uses backticks and ${} with no extra quotes.

3. Final Answer:

   type ID = `${string}-${number}`; -> Option A

4. Quick Check:

   Backticks + ${} = correct syntax [OK]

Hint: Use backticks and ${} without quotes for template types [OK]

Common Mistakes:

• Using single or double quotes instead of backticks
• Putting quotes inside ${} expressions
• Missing backticks around the pattern

3. What will be the result of this TypeScript code snippet?

type Email = `${string}@${string}.com`;

function isEmail(value: string): value is Email {
  return /.+@.+\.com$/.test(value);
}

console.log(isEmail('[e-mail]'));
console.log(isEmail('[e-mail]'));

medium

A. true\ntrue

B. false\ntrue

C. true\nfalse

D. false\nfalse

Solution

1. Step 1: Understand the Email type pattern

   The Email type expects strings like '[e-mail]'.

2. Step 2: Analyze the isEmail function

   The regex checks if the string ends with '.com' after an '@' symbol.

3. Step 3: Check the console.log outputs

   '[e-mail]' matches the regex, so true; '[e-mail]' does not, so false.

4. Final Answer:

   true false -> Option C

5. Quick Check:

   Regex matches .com only = true, false [OK]

Hint: Regex matches only .com emails, others return false [OK]

Common Mistakes:

• Assuming .org matches .com pattern
• Ignoring regex anchors
• Confusing true/false order in output

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

type Phone = `${number}-${number}-${number}`;

function isPhone(value: string): value is Phone {
  return /^\d{3}-\d{3}-\d{4}$/.test(value);
}

medium

A. The Phone type pattern does not match the regex format

B. The regex pattern is missing anchors

C. Template literals cannot use number types inside ${}

D. The function should return a boolean, not a type predicate

Solution

1. Step 1: Compare Phone type and regex pattern

   Phone type expects three numbers separated by dashes, but each ${number} matches any number, not fixed digits.

2. Step 2: Check regex pattern details

   The regex expects exactly 3 digits, then 3 digits, then 4 digits, which doesn't align with the Phone type's generic number placeholders.

3. Final Answer:

   The Phone type pattern does not match the regex format -> Option A

4. Quick Check:

   Type pattern and regex must align [OK]

Hint: Match template literal types exactly with regex patterns [OK]

Common Mistakes:

• Assuming ${number} matches fixed digit counts
• Ignoring regex anchors (though present here)
• Confusing return type of type predicate functions

5. Given this TypeScript code, what will be the output?

type UserID = `user_${number}`;

function parseUserID(id: string): UserID | null {
  if (id.match(/^user_\d+$/)) {
    return id as UserID;
  }
  return null;
}

console.log(parseUserID('user_123'));
console.log(parseUserID('admin_123'));

hard

A. null\nnull

B. 'user_123'\nnull

C. 'user_123'\n'user_123'

D. null\n'user_123'

Solution

1. Step 1: Understand UserID type pattern

   UserID must start with 'user_' followed by a number.

2. Step 2: Analyze parseUserID function

   The function returns the id cast as UserID if it matches the regex /^user_\d+$/, else returns null.

3. Step 3: Evaluate console.log outputs

   'user_123' matches regex, so returns 'user_123'; 'admin_123' does not, so returns null.

4. Final Answer:

   'user_123' null -> Option B

5. Quick Check:

   Regex match returns id, else null [OK]

Hint: Regex match controls return; unmatched returns null [OK]

Common Mistakes:

• Assuming 'admin_123' matches user pattern
• Confusing return types with casting
• Ignoring regex anchors and pattern