Part 5
2 chapters
Schema Evolution & the Living Contract
Design and evolve a schema without breaking clients, enforced by a breaking-change gate in CI.
Chapter 10
Schema design patterns
How the tracking view's schema is designed from the screens that read it: naming conventions, Node and global ids with Query.nodes, objects instead of foreign keys, interfaces and unions, one input and one payload per mutation, and conventions checked mechanically on the canonical SDL and on both live schemas.
Chapter 11
Evolution and versioning
How a GraphQL schema changes while clients depend on it: one schema without version numbers, safe, dangerous and breaking changes, nullability in both directions, the deprecation lifecycle on both stacks, and the breaking-change gate run on fixtures.