fullstack-slice

Coordinated multi-repo changes are automated by enforcing a contract-first workflow for your .NET backend and React frontend. The process establishes API contracts before coding, applies backward-compatible backend changes, aligns the frontend, and runs tests in both repositories to verify cross-repo compatibility.

Contract-first development for full-stack features is the process of establishing and enforcing API contracts before coding begins. This mechanism keeps the backend and frontend synchronized, reduces integration risk, and ensures smaller footprints when implementing features or bug fixes across multiple repositories.

To ensure cross-repo compatibility when updating an API contract, implement backward-compatible backend changes first, then update the frontend. You must run tests in both repository contexts and update documentation contracts, client typings, and references to reflect the modifications before merging.

Yes, the contract-first workflow requires backward-compatible backend changes to minimize risk and ensure compatibility. By mandating backward compatibility, the process allows the React frontend to align with updates without breaking existing consumers during the cross-repo verification phase.

The best way to keep documentation synchronized is by enforcing contract-first updates that automatically update contracts, client typings, and references across both repositories. This ensures that documentation accurately reflects the coordinated changes made to the API boundary.

You should not use the contract-first multi-repo change approach for work that does not touch both the .NET backend and React frontend repositories. It is specifically designed for coordinated feature and bug work requiring cross-repo verification, so isolated single-repo changes do not require this overhead.