GraphQL Finland

Transcript

1. Building Type-safe GraphQL Servers
2. Johannes Schickling Based in San Francisco Co-founder & CEO @prisma @schickling @schickling
3. Building the data layer for modern applications OUR MISSION
4. GraphQL servers with Prisma
5. How Prisma works
6. Let’s talk about GraphQL servers
8. Forgot `args.input` wrapper
9. Typo (casing)
10. Forgot mutation
11. `userName` resolver missing
12. Not allowed to return `null`
13. GraphQL Types, Resolvers & Models
14. Problems of building GraphQL servers Code generation Schema-first Type-safety Lots of boilerplate needed for resolvers Inconsistency between resolvers and GraphQL schema Unclear mapping between GraphQL types and resolver return values
15. graphqlgen • Schema-first: Based on your GraphQL schema • Type-safe: Resolvers, arguments, parents… • Codegen based: Minimal boilerplate Now open-source: github.com/prisma/graphqlgen
16. Getting started • Option A: Starting from scratch • Bootstrap new GraphQL server via `npm init graphqlgen` • Option B: Add to existing project • `npm install --dev graphqlgen` • Manually create `graphqlgen.yml` config file • Import generated interface types in your resolvers
17. Usage workflow • Scenario: Add field to type in GraphQL schema backed by model • Run `graphqlgen`. Done. • Scenario: Add type to GraphQL schema • Run `graphqlgen`. Copy & implement scaffolded resolver file. • Scenario: Remove field in model • Run `graphqlgen`. Copy scaffolded resolver function.
18. graphqlgen.yml
19. Demo Set up a new GraphQL server Evolve GraphQL schema Connect to real database 1 2 3
20. Future of graphqlgen • More languages: NodeJS, Flow & Reason • Smarter scaffolding workflows • Plugin system & integrations: Prisma, Apollo, …
21. Key Takeaways Codegeneration for minimal boilerplate Schema-first to avoid inconsistencies Type-safety for safe mapping & great developer experience 1 2 3
22. Thank you @schickling @schickling