Why generic interfaces matter in Typescript

Introduction

Generic interfaces let us write flexible code that works with many types without repeating ourselves.

When you want one interface to work with different data types.

When you want to avoid writing the same interface for each type.

When you want to keep your code easy to change and maintain.

When you want to create reusable components or functions.

When you want to catch type errors early while keeping flexibility.

Syntax

Typescript

interface InterfaceName<T> {
  property: T;
  method(param: T): T;
}

The <T> is a placeholder for any type you choose later.

You can use any name instead of T, but T is common.

Examples

This interface Box can hold any type of content.

Typescript

interface Box<T> {
  content: T;
}

This Result interface can wrap any type of data with a success flag.

Typescript

interface Result<T> {
  success: boolean;
  data: T;
}

This interface uses two generic types to hold two different values.

Typescript

interface Pair<T, U> {
  first: T;
  second: U;
}

Sample Program

This program shows how one generic interface Container<T> can be used for different types like number and string. It avoids writing separate interfaces for each type.

Typescript

interface Container<T> {
  value: T;
  getValue(): T;
}

class NumberContainer implements Container<number> {
  value: number;
  constructor(value: number) {
    this.value = value;
  }
  getValue(): number {
    return this.value;
  }
}

class StringContainer implements Container<string> {
  value: string;
  constructor(value: string) {
    this.value = value;
  }
  getValue(): string {
    return this.value;
  }
}

const numBox = new NumberContainer(123);
const strBox = new StringContainer("hello");

console.log(numBox.getValue());
console.log(strBox.getValue());

Important Notes

Generic interfaces help keep your code DRY (Don't Repeat Yourself).

They improve code readability and type safety.

You can combine generics with classes, functions, and other interfaces.

Summary

Generic interfaces let you write one interface for many types.

They make your code flexible and reusable.

They help catch errors early by checking types.

Practice

1. What is the main benefit of using generic interfaces in TypeScript?

easy

A. They automatically generate user interfaces.

B. They make the code run faster at runtime.

C. They allow the same interface to work with different data types.

D. They replace the need for classes.

Solution

1. Step 1: Understand what generic interfaces do

   Generic interfaces let you define a structure that can work with any type, not just one fixed type.

2. Step 2: Identify the benefit

   This flexibility means you can reuse the same interface for different data types, making your code more flexible and reusable.

3. Final Answer:

   They allow the same interface to work with different data types. -> Option C

4. Quick Check:

   Generic interfaces = flexible types [OK]

Hint: Generic interfaces = one interface, many types [OK]

Common Mistakes:

• Thinking generics improve runtime speed
• Confusing generics with UI generation
• Believing generics replace classes

2. Which of the following is the correct syntax to declare a generic interface named Box with a type parameter T?

easy

A. interface Box { content: T; }

B. interface Box<T> { content: T; }

C. interface Box<T> { content: any; }

D. interface Box<T> content: T;

Solution

1. Step 1: Recall generic interface syntax

   Generic interfaces use angle brackets after the name to declare type parameters, like interface Name<T>.

2. Step 2: Check the property type

   The property should use the generic type parameter T to be flexible.

3. Final Answer:

   interface Box<T> { content: T; } -> Option B

4. Quick Check:

   Generic syntax = interface Name<T> { prop: T } [OK]

Hint: Generic interfaces use <T> after name [OK]

Common Mistakes:

• Omitting <T> after interface name
• Using any instead of generic type
• Missing curly braces or semicolons

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

interface Container<T> {
  value: T;
}

const numberContainer: Container<number> = { value: 42 };
const stringContainer: Container<string> = { value: 'hello' };

console.log(numberContainer.value);
console.log(stringContainer.value);

medium

A. 42 and hello

B. number and string

C. undefined and undefined

D. Error: Type mismatch

Solution

1. Step 1: Understand the generic interface usage

   The interface Container<T> holds a value of type T. Here, numberContainer uses number and stringContainer uses string.

2. Step 2: Check the console.log outputs

   Logging numberContainer.value prints 42, and stringContainer.value prints 'hello'.

3. Final Answer:

   42 and hello -> Option A

4. Quick Check:

   Generic interface values print correctly [OK]

Hint: Generic types keep values typed and accessible [OK]

Common Mistakes:

• Expecting type names instead of values
• Thinking generics cause runtime errors
• Confusing property access syntax

4. Identify the error in this generic interface usage:

interface Pair<T> {
  first: T;
  second: T;
}

const pair: Pair = { first: 1, second: 'two' };

medium

A. Syntax error in object declaration

B. Cannot mix number and string in Pair

C. Interface Pair cannot have two properties

D. Missing type argument when using Pair

Solution

1. Step 1: Check generic interface usage

   The interface Pair<T> requires a type argument when used, like Pair<number>.

2. Step 2: Identify the error in the code

   The variable pair is declared as Pair without specifying <T>, causing a TypeScript error.

3. Final Answer:

   Missing type argument when using Pair -> Option D

4. Quick Check:

   Generic interfaces need type arguments [OK]

Hint: Always specify type argument when using generic interfaces [OK]

Common Mistakes:

• Omitting the generic type argument
• Trying to mix types without union
• Assuming interface limits property count

5. Given this generic interface and usage, what is the best way to ensure the data property can hold either a string or an array of strings without losing type safety?

interface Response<T> {
  data: T;
}

const response1: Response<string> = { data: 'hello' };
const response2: Response = { data: ['hello', 'world'] };

// How to declare a variable that can hold either response1 or response2?

hard

A. Use a union type: Response

B. Use any type: Response<any>

C. Create two separate interfaces for string and string[]

D. Use Response<object> to cover both

Solution

1. Step 1: Understand the need for flexible but safe typing

   We want a variable that can hold either a string or an array of strings, keeping type safety.

2. Step 2: Use union types with generics

   Declaring Response<string | string[]> allows data to be either type safely.

3. Final Answer:

   Use a union type: Response<string | string[]> -> Option A

4. Quick Check:

   Union types + generics = flexible and safe [OK]

Hint: Use union types inside generics for multiple allowed types [OK]

Common Mistakes:

• Using any loses type safety
• Creating duplicate interfaces wastes code
• Using object is too broad and unsafe