Write better queries & mutations
summary
Advocates designing queries and mutations as functions: use single required input to reduce call permutations (example reduces nine possible calls to one), pick descriptive names so intent is documented, and prefer finer-grain updates like updateUserEmail with required inputs. Use custom scalars (email) and enums to narrow types, require inputs and minimize nullable inputs, but make output fields nullable to preserve schema evolution. When generalizing, provide sensible defaults and avoid overly generic names to keep client overhead low.
AI-written summary · about
chapters (6)
related talks
25mOptimizing GraphQL Applications
29mWrite Queries, Not Code
23mImproving User Experiences with a Nullable Schema
22m5 Antipatterns that Made Our React/GraphQL App Slow (And How We Fixed Them)
33mEvolving GraphQL Schemas
49mCash in Your Change: Convert Mutations to AI Insights
24mA GraphQL Survival Kit
01h 28mWorkshop: Demand-Driven Schema Design