Why advanced generics matter in Typescript - See It in Action

Why advanced generics matter

📖 Scenario: Imagine you are building a simple library system. You want to keep track of books and users, but you want your code to be flexible so it can work with different types of items and users in the future.

🎯 Goal: Build a TypeScript program that uses advanced generics to create a flexible library system. You will create a generic function that can handle different types of items and users, showing why advanced generics help write reusable and safe code.

📋 What You'll Learn

Create a generic interface called LibraryItem with a property id of type T

Create a generic interface called User with a property userId of type U

Create a generic function called checkoutItem that takes a LibraryItem and a User and returns a string message

Use advanced generics to ensure the function works with any types for id and userId

Print the result of calling checkoutItem with a book and a user

💡 Why This Matters

🌍 Real World

Advanced generics let developers write code that works with many data types without repeating code. This is useful in libraries, frameworks, and large applications.

💼 Career

Understanding advanced generics is important for TypeScript developers to build scalable and maintainable codebases that handle diverse data safely.

1

Create generic interfaces for library items and users

Create a generic interface called LibraryItem with a property id of type T. Also create a generic interface called User with a property userId of type U.

Typescript

// Your code here

Hint

Use interface keyword and generic type parameters <T> and <U>.

2

Create a generic function to checkout items

Create a generic function called checkoutItem with type parameters T and U. It should take two parameters: item of type LibraryItem<T> and user of type User<U>. The function should return a string.

Typescript

interface LibraryItem {
  id: T;
}

interface User {
  userId: U;
}

// Your code here

Hint

Use generic type parameters <T, U> and template strings for the return.

3

Create example book and user objects

Create a constant book of type LibraryItem<number> with id 101. Create a constant user of type User<string> with userId 'user123'.

Typescript

interface LibraryItem {
  id: T;
}

interface User {
  userId: U;
}

function checkoutItem(item: LibraryItem, user: User): string {
  return `User ${user.userId} checked out item ${item.id}`;
}

// Your code here

Hint

Use const and specify the generic types explicitly.

4

Call the function and print the result

Call the function checkoutItem with book and user as arguments. Print the returned string using console.log.

Typescript

interface LibraryItem {
  id: T;
}

interface User {
  userId: U;
}

function checkoutItem(item: LibraryItem, user: User): string {
  return `User ${user.userId} checked out item ${item.id}`;
}

const book: LibraryItem = { id: 101 };
const user: User = { userId: 'user123' };

// Your code here

Hint

Use console.log(checkoutItem(book, user)) to print the message.

Practice

1. What is the main benefit of using advanced generics in TypeScript?

easy

A. They automatically fix bugs in your code.

B. They make the code run faster at runtime.

C. They allow writing flexible and reusable code with type safety.

D. They replace the need for functions.

Solution

1. Step 1: Understand what generics do

   Generics let you write code that works with many types without losing type safety.

2. Step 2: Identify the main benefit

   Advanced generics improve flexibility and reusability while preventing type errors.

3. Final Answer:

   They allow writing flexible and reusable code with type safety. -> Option C

4. Quick Check:

   Advanced generics = flexible reusable type-safe code [OK]

Hint: Think: generics = flexible + safe code [OK]

Common Mistakes:

• Confusing generics with runtime performance improvements
• Believing generics fix bugs automatically
• Thinking generics replace functions

2. Which of the following is the correct syntax to declare a generic function in TypeScript?

easy

A. function example(arg: T): T { return arg; }

B. function example<T>(arg: T): void { return arg; }

C. function example<T>(arg): T { return arg; }

D. function example<T>(arg: T): T { return arg; }

Solution

1. Step 1: Check generic syntax

   Generic functions declare a type parameter inside angle brackets after the function name.

2. Step 2: Verify parameter and return types

   The argument and return type should use the generic type parameter T.

3. Final Answer:

   function example<T>(arg: T): T { return arg; } -> Option D

4. Quick Check:

   Generic function syntax = function name<T>(arg: T): T [OK]

Hint: Generic syntax: function name<T>(arg: T): T [OK]

Common Mistakes:

• Omitting the generic parameter declaration <T>
• Not typing the argument with T
• Returning a value in a void function

3. What will be the output of this TypeScript code?

function wrapInArray<T>(value: T): T[] {
  return [value];
}

const result = wrapInArray(42);
console.log(result);

medium

A. [42]

B. 42

C. undefined

D. Error: Type mismatch

Solution

1. Step 1: Understand the function behavior

   The function takes a value of any type T and returns an array containing that value.

2. Step 2: Apply the function to the input

   Calling wrapInArray(42) returns [42], an array with the number 42 inside.

3. Final Answer:

   [42] -> Option A

4. Quick Check:

   wrapInArray(42) = [42] [OK]

Hint: Generic function returns array with input inside [OK]

Common Mistakes:

• Expecting just the value instead of an array
• Thinking it returns undefined
• Confusing type errors with runtime output

4. Identify the error in this TypeScript generic function:

function identity<T>(arg: T): T {
  return arg.length;
}

medium

A. The function returns a number but declares return type T.

B. The generic type T is not declared correctly.

C. The argument arg should not be generic.

D. There is no error in this function.

Solution

1. Step 1: Analyze the return statement

   The function returns arg.length, which is a number.

2. Step 2: Check return type consistency

   The function declares it returns type T, but number may not be T, causing a type mismatch.

3. Final Answer:

   The function returns a number but declares return type T. -> Option A

4. Quick Check:

   Return type mismatch = error [OK]

Hint: Return type must match declared generic type [OK]

Common Mistakes:

• Assuming arg always has length property
• Ignoring return type mismatch
• Thinking generic declaration is wrong

5. Given this generic interface and function, what is the correct way to use advanced generics to ensure type safety?

interface Container<T> {
  value: T;
}

function getValue<T>(container: Container<T>): T {
  return container.value;
}

const numberContainer = { value: 123 };
const stringContainer = { value: "hello" };

// Which call is correct?

hard

A. getValue(stringContainer);

B. getValue<number>(numberContainer);

C. getValue<number>(stringContainer);

D. getValue<string>(numberContainer);

Solution

1. Step 1: Match generic type with container value

   numberContainer has value of type number, so T should be number.

2. Step 2: Check each option for type safety

   getValue<number>(numberContainer); uses getValue<number>(numberContainer), which matches types correctly.

3. Final Answer:

   getValue<number>(numberContainer); -> Option B

4. Quick Check:

   Generic type matches container value type [OK]

Hint: Generic type must match container's value type [OK]

Common Mistakes:

• Passing wrong generic type for container value
• Omitting generic type when explicit needed
• Mixing container types incorrectly