How not to break GraphQL clients?
summary
Explains which schema changes actually break clients and which tools miss nuances, using GraphQL.js’s safe / breaking / dangerous categories, concrete fixes like deprecate and duplicate fields with a sunset reason and when default argument values prevent validation errors. Gives safe conversions (for example string→ID and int→float are safe), shows union/interface pitfalls and recommends using __typename to detect unknown union variants, and warns removing executable directives (like skip) causes validation failures.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:14Types and Fields
- 3:35Changing Field Kind X
- 4:40Arguments
- 8:16Changing default value of Argument A
- 12:14Removal of type from Union X
- 13:15implementation
- 17:16Directives
- 19:29Removing a directive location X
related talks
32mHow to Not Break Your GraphQL Clients
23mHandling breaking changes in a GraphQL schema
49mGraphQL Schema Design — Building Schemas Correctly (version 2)
24mA GraphQL Survival Kit
01h 11mGraphQL: 'Dangerous' Advice. Why Use GraphQL When There’s REST?
39mDon't Panic: A Developer's Guide to Building Secure GraphQL APIs
30mThe Biggest Change To GraphQL Codegen in 10 Years
30mWhy GraphQL vs. Why not GraphQL