TypeScript & Architecture

Code Review: Bad TypeScript Design

easyCode ReviewJS / TS

Problem Statement

Review the following TypeScript data mapper. Identify type safety flaws, excessive `any` usage, unsafe type assertions (`as any`), and weak interfaces. Refactor for strict type safety.

Code under review

JAVASCRIPT• handler.js
// Unsafe data normalization pipeline
function processApiResponse(data) {
  const result = (data as any).items.map((item) => {
    return {
      id: item.id as string,
      title: item.title || "Untitled",
      meta: (item as any).metadata ? JSON.parse((item as any).metadata) : {}
    };
  });

  return result as any;
}

Read only. Write down what you would flag below, then compare with the reference notes.

JavaScript & TypeScript versions included
Run this as a live interview

Practice solo

Write down what you would flag in this code, then compare it with the reference notes.

Write your findings first, then check yourself against the notes.

Get new interview exercises

Practice problems and review drills, sent when we publish new ones. No spam.

Unsubscribe anytime. We never share your address.