typescript-types-expert

TypeScript type auditing analyzes type usage for correctness, adherence to patterns like colocation and import discipline, and potential issues. It provides a health report to identify anti-patterns before merging new data models.

Fixing unsafe type assertions involves correcting common type errors and anti-patterns by aligning with Zod schemas and enforcing NullableString handling. This replaces manual validation with safer, schema-driven type definitions.

Designing TypeScript types for API integration requires guiding the creation of new types according to project conventions for location and structure. This ensures type safety and prevents inline API type definitions and direct gateway imports.

Direct gateway import issues occur when type definitions bypass established project conventions. Auditing identifies these structural inconsistencies, ensuring import discipline and proper colocation principles are maintained across the codebase.

Yes, Zod schema alignment enforces type safety by replacing manual validation and unsafe type assertions with structured schema definitions. This ensures runtime validation matches static TypeScript types seamlessly.

Colocation principles for TypeScript types are needed when designing new features to ensure type definitions follow project conventions for location and structure. This maintains code quality and prevents structural inconsistencies during type auditing.