Category · GraphQL
The client asks for exactly the fields it shows
Why GraphQL after REST, the schema and types, queries with variables, mutations and resolvers, N+1 and DataLoader, enum, input, and union, errors and permissions, pagination, the client and its cache. The practice is real resolvers in JS.
To the first lessonCheatsheet nowTopics, each as its own lesson
01Why GraphQLDemoOne endpoint, one request, exactly the fields you need.
9 min
02Schema and typestype, fields, ! and lists. Query is the entry point for reads.
10 min
03Queries, variables, fragmentsA query is a tree of fields. Variables replace string concatenation.
10 min
04Mutations and resolversA resolver is a function that knows where to get a field.
12 min
05N+1 and DataLoaderTen books, ten queries for authors. DataLoader makes one.
12 min
06enum, input, interface, unionTypes that make a schema precise: limited values, input objects, shared fields.
12 min
07Errors, context, and permissionsIn GraphQL an error is part of the response, not just a status.
11 min
08Pagination: cursors and Connectionedges, node, pageInfo — verbose, but the feed doesn't break.
11 min
09The client: fetch, cache, and updatesA GraphQL request is an ordinary POST. The rest is client-library convenience.
11 min0/9 topics open. This is the course intro, not the whole course on one page.