E2E type safety with GraphQL
About me 🤓
- Write code! - mostly for fun 😃
- Love to play Football ⚽
- Working with Prisma (prisma.io) on OSS 😼
- Twitter (and across internet): @divyenduz 🐦
Dynamic Languages 🎃
- Javascript
- PHP
- Python
Typed Languages 😼
- Scala
- Haskell
- Java
- Typescript 👀
Advantages of types!
- Static analysis
- Autocompletion
- Contract across interfaces (API)
Are types important?
- Large scale code bases (Flow, TS, Pyre)
- CI/CD - Interface contracts
- Code generation 🤔
Downsides of type safety
- Verbosity 🤯
- Learning curve 📈
Code generation
To the rescue!
GraphQL is strongly typed
- Introspect to generate type interfaces
- Introspect to scaffold resolvers
- Profit via "graphql-resolver-codegen"
Demo
Note: Demo interfaces and scaffolding generation for a GraphQL schema for Typescript but do mention that the tool itself is language agnostic.
Challenges
- Keeping resolvers up to date
- Workflow for running the generation
- Developer experience