Why should you care?

One paginated list component should work for Account, Order, and Patient types.

See it live — copy this example

Paste into your MeanVerse project (Angular + Express + MongoDB), then run with ng serve / node / mongosh as noted.

export interface Paginated<T> {
  items: T[];
  total: number;
  page: number;
}

export function firstItem<T>(list: T[]): T | undefined {
  return list[0];
}

// Angular service
getAccounts(): Observable<Paginated<Account>> {
  return this.http.get<Paginated<Account>>('/api/accounts?page=1');
}

What happened?

• Paginated wraps any item type.
• HttpClient.get> ensures items are Account[], not unknown.

Practice next

1. Write Paginated interface used by three resources.
2. Create generic TableComponent.
3. Use keyof T for sort column typing.
4. Add generic Result for success/error union.
5. Build cache Map helper function.

Remember

Generics = types as parameters. Reuse list/table/API wrappers safely. Angular HttpClient relies heavily on generics.

Admin data grids

MeanVerse admin shows typed columns for any entity T.

Outcome: One grid component; compile errors if column key wrong.