Having Your Cake and Eating It Too — GraphQL in Reason
summary
Claims that full-stack type safety is practical: ReasonML clients get generated bindings and in-editor autocomplete from GraphQL schemas, back ends use ocaml-graphql-server and CI diffs to block breaking changes, and a JSON-to-type tool with example-driven novelty tracking reduces decoder boilerplate. Demos show automatic Reason types from GitHub responses, cross‑API queries spanning YouTube/Twitter, and runtime errors eliminated in practice, so the stack actually builds, runs, and prevents client breaks.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:27Introduction
- 3:07Reason Ml
- 9:50External Api
- 11:08Parse Person Json
- 12:49Real World Example
- 15:22Github Rest Api
- 22:55Introspection
- 25:35Autocomplete
related talks
20mReasonable Reasons for ReasonML
40mBrief Introduction to ReasonML
27mReasonML for Skeptics
35mFull-stack Type Safety with React, GraphQL, and TypeScript
47mRock-Solid Components with TypeScript and GraphQL
26mFull Stack Type Safety with React, GraphQL, and TypeScript
10mIntroduction to ReasonML- 40mBrief Introduction to ReasonML