End to End type safety: A tale of three domains
summary
Argument: enforce consistent types from DB to client using TypeScript, Prisma, and graphql-code-generator. Demonstration changes a Boolean isPersonal into a database enum category, runs a migration, fixes the seed script, regenerates Prisma and GraphQL types, then updates the client queries; each step produces compiler errors that point to exact fixes. Claim: end-to-end type safety catches cross‑layer mismatches, speeds refactors, and the demo workflow works end‑to‑end for this blog app.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:43What is type safety?
- 4:46What is end-to-end type safety?
- 5:19Communication across domains
- 7:39Why is end-to-end type safety useful?
- 10:19How to implement end to end type safety?
related talks
25mType-safe GraphQL with TypeScript
35mFull-stack Type Safety with React, GraphQL, and TypeScript
30mZero-cost Type Safety for your Database with Prisma
10mEnd-to-end Type Safety
26mFull Stack Type Safety with React, GraphQL, and TypeScript
29mType safety from the database to the frontend
34mAchieving end to end typesafety
27mWeb applications of the future with TypeScript and GraphQL