React & GraphQL - Bringing Simplicity and Correctness to Client Side Development
summary
A working GitHub user search and profile page demonstrates React components co‑locating GraphQL queries and fragments, using Apollo Client to hit GitHub v4 GraphQL with queries that are composed from component fragments, mutations that toggle stars and update the normalized cache, and autogenerated TypeScript types that catch bugs. The composed page request is about 8 kilobytes over the wire versus dozens to hundreds of kilobytes and impossible queries with the REST API, and the demo UI and cache updates work end to end.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:37Chris Toomey
- 2:13You Get What You Ask For
- 3:50Get Related Resources in a Single Query
- 4:53Schema & Type System
- 8:46How Does GraphQL Fit with React?
related talks
58mCrafting compelling real-time web experiences with GraphQL and React
27mReact State Management In a GraphQL Era
47mReact, Relay and GraphQL — a perfectly normal component approach
25mReact state management in a GraphQL era
30mGraphQL in the Era of React Server Components
26mEverything You Need to Know About GraphQL in 3 Components
34mCreate Flexible React Applications Using GraphQL APIs
22m5 Antipatterns that Made Our React/GraphQL App Slow (And How We Fixed Them)