Why Generic interface for collections in Typescript? - Purpose & Use Cases

The Big Idea

What if you could write one piece of code that works perfectly for any collection, no matter the type?

The Scenario

Imagine you have different types of collections like lists of numbers, strings, or even custom objects. You want to write functions that work with all these collections, but you have to write separate code for each type.

The Problem

Writing separate code for each collection type is slow and repetitive. It's easy to make mistakes when copying and changing code. Also, if you want to add a new type, you must write even more code, which is frustrating and error-prone.

The Solution

Using a generic interface lets you write one flexible blueprint that works with any type of collection. This saves time, reduces errors, and makes your code easier to maintain and extend.

Before vs After

✗ Before

interface NumberCollection { items: number[]; }
interface StringCollection { items: string[]; }

✓ After

interface Collection<T> { items: T[]; }

What It Enables

It enables you to create reusable, type-safe code that works with any kind of collection without rewriting or duplicating logic.

Real Life Example

Think of a music app that manages playlists of songs, podcasts, or audiobooks. A generic collection interface lets the app handle all these media types with the same code, making it easier to add new media types later.

Key Takeaways

Manual code for each collection type is repetitive and error-prone.

Generic interfaces provide a flexible, reusable blueprint for collections.

This approach saves time and makes your code easier to maintain and extend.