The Pitfalls of Generated TypeScript from a GraphQL Schema
summary
Examines pitfalls when using generated TypeScript contracts from a GraphQL schema, naming TypeScript and GraphQL as the technologies. Describes non-obvious issues that arise from server–client generated code, shows real-world developer challenges and consequences of blindly following generated contracts, and explores where subtle bugs or mismatches can hide.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 4:21Frontend GraphQL dependency
- 11:38Auto-generated types pitfalls
- 18:36Architecture struggles & fixes
- 24:18GraphQL as architecture
- 26:52Abstracting GraphQL data
- 33:35Key tech questions
- 35:03Q&A
related talks
07mManaging TypeScript and GraphQL types in Node
47mRock-Solid Components with TypeScript and GraphQL
25mType-safe GraphQL with TypeScript
27mWeb applications of the future with TypeScript and GraphQL
06mAutomagic TypeScript Codegen for GraphQL
25mWeb applications of the future with TypeScript and GraphQL
57mType safe GraphQL with TypeScript
29mType safety from the database to the frontend
