Why generic interfaces matter in Typescript - Challenge Your Understanding

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of generic interface usage

What is the output of this TypeScript code using a generic interface?

Typescript

interface Box<T> {
  content: T;
}

const numberBox: Box<number> = { content: 123 };
const stringBox: Box<string> = { content: "hello" };

console.log(typeof numberBox.content, typeof stringBox.content);

A "number string"

B "number number"

C "object object"

D "string number"

💡 Hint

Think about the types of the content property in each box.

The numberBox.content is a number, so typeof returns "number". The stringBox.content is a string, so typeof returns "string". The console.log prints both separated by a space.

🧠 Conceptual

intermediate

Why use generic interfaces?

Why are generic interfaces important in TypeScript?

A They allow defining reusable interfaces that work with any data type, improving code flexibility.

B They enforce using only one specific data type in all interface instances.

C They automatically convert all data types to strings inside the interface.

D They prevent interfaces from being extended or reused.

💡 Hint

Think about how generics help avoid repeating similar interfaces for different types.

Generic interfaces let you write one interface that can handle many types, making your code more flexible and reusable.

🔧 Debug

advanced

Identify the error in generic interface usage

What error will this TypeScript code produce?

Typescript

interface Container<T> {
  value: T;
}

const c: Container = { value: 42 };

A No error, code runs fine.

B Error: Property 'value' is missing in type '{}'.

C Error: Type 'number' is not assignable to type 'string'.

D Error: Generic type 'Container<T>' requires 1 type argument(s).

💡 Hint

Check if the generic type parameter is provided when using the interface.

The interface Container requires a type argument like Container. Omitting it causes a TypeScript error.

📝 Syntax

advanced

Correct syntax for generic interface with multiple types

Which option correctly defines a generic interface with two type parameters?

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

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

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

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

💡 Hint

Remember how to separate multiple generic parameters in TypeScript.

Generic parameters must be separated by commas inside angle brackets. Option B is correct syntax.

🚀 Application

expert

Using generic interfaces to enforce type safety

Given this generic interface, what is the type of result after this code runs?

interface Response {
  data: T;
  error?: string;
}

function fetchData(input: T): Response {
  return { data: input };
}

const result = fetchData({ id: 1, name: "Alice" });

A { data: object; error?: string | undefined }

B { data: any; error?: string | undefined }

C { data: { id: number; name: string }; error?: string | undefined }

D { data: string; error?: string | undefined }

💡 Hint

Look at how the generic type T is inferred from the argument.

The generic type T is inferred as { id: number; name: string }. So result has data of that exact type.

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