api-contract-validator

Purpose

Ensures type safety and consistency between frontend TypeScript interfaces and backend Pydantic models by detecting field name differences, type mismatches, and missing fields.

When to Use

• When validating API contracts before a release.
• When identifying breaking changes in data models between frontend and backend.
• When standardizing property casing (camelCase vs snake_case) across the stack.

Process

1. Scan TypeScript interfaces:
   • Read frontend API service files (frontend/src/api/*.ts)
   • Extract TypeScript interfaces for requests/responses
   • Parse field types, optional fields, arrays, enums
   • Build TypeScript type inventory