Contracts
Backward Compatibility in APIs: Fields, Enums, and Behavioral Changes
How to tell a compatible API change from a breaking one, using JSON Schema keywords and Google's AIP-180 as a published guide rather than a universal law.
Technical notes
Section
Notes here treat the contract as the promise a client can rely on, including changes that a schema file does not show.
Contracts
How to tell a compatible API change from a breaking one, using JSON Schema keywords and Google's AIP-180 as a published guide rather than a universal law.
Contracts
A three-phase sequence, expand then migrate then contract, for changing an API contract while old clients keep working, with rollback called out as its own case.