End-to-End Type Safety with Swagger and TypeScript
summary
Claims a working pipeline that moves types from server to client using Swagger/OpenAPI, TypeScript, protocol buffers and gRPC, with concrete fixes Lyft saw during a full TypeScript migration and examples of bugs caught and missed. Shows middleware that rejects nonconforming requests, generated TypeScript clients driven from OpenAPI or protobuf, annotations for Nest-style handlers, a watcher that regenerates SDKs, and plans for gRPC in the browser and protobuf-backed single source of truth.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:18Chrome bug
- 2:17Bugs
- 4:52TypeScript Migration
- 8:58What happened
- 15:08APR
- 21:38Protocol Buffers
related talks
45mType-Safe APIs - Syncing Back & Front End Types w/ Code Generation
29mCrafting Reliable and Testable Code with TypeScript
10mEnd-to-end Type Safety
27mWeb applications of the future with TypeScript and GraphQL
39mEnd to end typing for web applications
34mAchieving end to end typesafety
24mEnd to End type safety: A tale of three domains
31mBuilding an OpenAPI from Typescript