types-schemas

To sync TypeScript types and JSON schemas across services, you update shared type definitions in src/types and schema contracts in src/types/schemas, then run schema_index.py and validate type checks to maintain cross-layer data contract integrity.

Mismatched data structures occur when API, frontend, and extension layers lack centralized contracts. Synchronizing shared TypeScript type definitions and JSON schema contracts in a single repository ensures cross-layer consistency and prevents integration errors.

The best way to manage shared JSON schemas in a TypeScript codebase is centralizing them in src/types/schemas and executing schema_index.py to validate type checks, ensuring all services reference identical contract definitions.

Yes, you need to run the schema_index.py validation script after updating shared TypeScript type definitions. Executing this script and validating type checks guarantees that cross-layer data contracts remain consistent throughout the Madoc services.

Yes, you can update a new API field and propagate changes across all services by modifying the shared TypeScript type and corresponding JSON schema in one centralized location, specifically within the src/types directory of the Madoc codebase.

Synchronizing TypeScript schemas is limited to projects under services/madoc-ts, requiring updates specifically within src/types and src/types/schemas directories to ensure cross-layer data contracts remain consistent and valid.