Generic Interfaces

A generic interface describes a reusable object contract parameterized by one or more types.

What you will learn: the purpose of generic interfaces, the rules TypeScript checks, and what its JavaScript behavior looks like in a runnable example.

The chosen type parameter can be used consistently in fields and methods, such as a response containing data: T. Interfaces vanish in JavaScript output; only the concrete value exists while the program runs.

Key distinction: TypeScript checks the declared types during development; emitted JavaScript carries out the value-level operation at runtime. A type declaration alone never validates untrusted runtime input.

Read this illustration from the first labeled part to the last. Compare it with the example and identify which parts are type checks and which parts run in JavaScript.

This self-contained example uses fixed values, so it runs without reading input or depending on an external service. Paste it into the TypeScript Playground or save it as main.ts.

TypeScript program

interface ResponseData<T> {
  ok: boolean;
  data: T;
}
const answer: ResponseData<{ id: number; title: string }> = {
  ok: true,
  data: { id: 3, title: "Guide" }
};
console.log(answer.ok);
console.log(`${answer.data.id}: ${answer.data.title}`);

Verified output

true
3: Guide

Run locally: npx tsc --strict --target es2022 --module commonjs main.ts, then node main.js. For projects with a tsconfig.json, build using that configuration instead.

T substitutes the object type containing id and title. The data object satisfies that shape, so its members are available with their own types. JavaScript prints true and 3: Guide.

Check each step: identify the input values, follow the JavaScript operation in execution order, and match the final expression with the exact output shown. An annotation can reject invalid source before execution, but does not change the value printed.

Do not treat ResponseData<T> as a runtime schema validator for downloaded JSON. Validate remote data separately.

How to debug: reproduce the issue in a minimal example. For compiler errors, inspect the inferred and declared types; for a runtime surprise, log the actual values and follow their references or branches.

Add an optional error?: string field and create a second response for a failed operation.

Practice routine: predict the result on paper, edit one part of the code, compile under --strict, run the JavaScript, and explain whether TypeScript caught an error or JavaScript simply behaved differently.

Generic Interfaces: A generic interface describes a reusable object contract parameterized by one or more types.

T substitutes the object type containing id and title. The data object satisfies that shape, so its members are available with their own types. JavaScript prints true and 3: Guide.

Before continuing, explain one valid use case, one common pitfall, and the separation between compile-time checking and runtime behavior for this feature.