Why Generic interface declaration in Typescript? - Purpose & Use Cases

The Big Idea

What if one simple blueprint could fit all your different needs perfectly?

The Scenario

Imagine you want to create a blueprint for different types of boxes, like a box for books, a box for toys, or a box for clothes. You try to write a separate blueprint for each box type manually.

The Problem

Writing a new blueprint for every box type is slow and boring. If you want to change something common, you must update every blueprint separately, which can cause mistakes and wastes time.

The Solution

Using a generic interface lets you create one flexible blueprint that works for any box type. You just tell it what kind of box you want when you use it, so it adapts automatically without rewriting.

Before vs After

✗ Before

interface BookBox { content: Book; }
interface ToyBox { content: Toy; }

✓ After

interface Box<T> { content: T; }

What It Enables

It lets you build reusable and adaptable blueprints that save time and reduce errors by handling many types with one simple interface.

Real Life Example

Think of an online store that sells many products. Using a generic interface for product details means the store can handle books, electronics, or clothes all with the same code structure.

Key Takeaways

Manual separate interfaces are slow and error-prone.

Generic interfaces create one flexible template for many types.

This approach saves time and makes code easier to maintain.

Practice

1. What does the <T> represent in a TypeScript generic interface declaration?

easy

A. A special type that only accepts strings

B. A variable name for a function

C. A keyword to declare a constant

D. A placeholder for a type that will be specified later

Solution

1. Step 1: Understand generic syntax

   The <T> syntax in TypeScript is used to declare a generic type parameter, which acts as a placeholder for a type.

2. Step 2: Identify the role of T

   This placeholder allows the interface to be flexible and reusable with different types specified later.

3. Final Answer:

   A placeholder for a type that will be specified later -> Option D

4. Quick Check:

   Generic <T> = Type placeholder [OK]

Hint: Remember <T> means 'type to be given later' [OK]

Common Mistakes:

• Thinking T is a variable or constant
• Confusing <T> with a function parameter
• Assuming T is always a string type

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<T> = { content: T; }

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

C. interface Box<T> content: T;

D. interface Box { content: T; }

Solution

1. Step 1: Check interface declaration syntax

   In TypeScript, interfaces are declared with the keyword interface followed by the name and optional generic parameters in angle brackets.

2. Step 2: Verify correct use of braces and type parameter

   The correct syntax includes curly braces to define the interface body and uses <T> to declare the generic type parameter.

3. Final Answer:

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

4. Quick Check:

   Generic interface syntax = interface Box<T> { content: T; } [OK]

Hint: Generic interfaces need <T> and braces {} [OK]

Common Mistakes:

• Omitting the generic parameter <T>
• Missing curly braces around interface body
• Using equals sign instead of braces

3. Given the interface declaration:

interface Container<T> { value: T; }

What is the output of this code?

const numberContainer: Container<number> = { value: 42 };
console.log(numberContainer.value);

medium

A. Error: Type mismatch

B. undefined

C. 42

D. null

Solution

1. Step 1: Understand the generic interface usage

   The interface Container<T> expects a type parameter. Here, number is specified, so value must be a number.

2. Step 2: Analyze the assigned object and console output

   The object { value: 42 } matches the interface with value as a number. Logging numberContainer.value prints 42.

3. Final Answer:

   42 -> Option C

4. Quick Check:

   Generic with number type outputs 42 [OK]

Hint: Generic type sets property type; output matches assigned value [OK]

Common Mistakes:

• Expecting a runtime error due to generics
• Confusing generic type with runtime type enforcement
• Assuming output is undefined or null

4. Identify the error in this generic interface usage:

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

const pair: Pair = { first: 'hello', second: 'world' };

medium

A. Missing generic type argument when using Pair

B. Properties first and second should be numbers

C. Interface Pair cannot have two properties of the same type

D. Object literal syntax is incorrect

Solution

1. Step 1: Check interface usage with generics

   The interface Pair<T> requires a type argument when used. Here, Pair is used without specifying <T>.

2. Step 2: Identify the missing generic argument error

   TypeScript will report an error because the generic type parameter is missing when declaring pair.

3. Final Answer:

   Missing generic type argument when using Pair -> Option A

4. Quick Check:

   Generic interface usage needs type argument [OK]

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

Common Mistakes:

• Forgetting to add <Type> when using generic interfaces
• Assuming default type if omitted
• Confusing property types with generic parameter

5. You want to create a generic interface Result<T> that holds a data property of type T and a success boolean. Which of the following implementations correctly uses this interface to type a variable holding a string result?

hard

A. const res: Result<string> = { data: 'Done', success: true };

B. const res: Result<string> = { data: 123, success: true };

C. const res: Result = { data: 'Done', success: true };

D. const res: Result<number> = { data: 'Done', success: true };

Solution

1. Step 1: Understand the generic interface requirements

   The interface Result<T> expects a data property of type T and a success boolean.

2. Step 2: Check each option for correct type usage

   const res: Result<string> = { data: 123, success: true }; assigns a number to data but expects a string type, so it's incorrect.
   const res: Result<string> = { data: 'Done', success: true }; correctly assigns a string to data and includes success.
   const res: Result = { data: 'Done', success: true }; omits the generic type argument, which is required.
   const res: Result<number> = { data: 'Done', success: true }; uses number type but assigns a string, causing a type mismatch.

3. Final Answer:

   const res: Result<string> = { data: 'Done', success: true }; -> Option A

4. Quick Check:

   Generic type matches property type = const res: Result<string> = { data: 'Done', success: true }; [OK]

Hint: Match generic type with property value type exactly [OK]

Common Mistakes:

• Assigning wrong type to generic property
• Omitting generic type argument
• Mixing up generic type parameters