Building Tooling That Speaks GraphQL
summary
Postman’s GraphQL client uses graphql.js to parse documents into ASTs, then visits those ASTs to build tools: an ESLint rule that flags @deprecated usages and auto-reports a JIRA ticket, a cross-repo search that finds 100+ usages before removal, and a query editor that autocompletes using TypeInfo to keep parent type context. Workflow leverages AST Explorer, prettier and graphql-config; Apollo’s parser is noted as more error‑resilient but the JS toolchain proves practical and effective.
AI-written summary · about
chapters (9)
- 0:00Introduction to GraphQL tooling
- 1:25Existing GraphQL tools worth using
- 2:49Parsing GraphQL documents into AST
- 6:39Visitors and AST transformations
- 9:30Detecting deprecated fields with ESLint
- 12:19Schema-aware GraphQL analysis
- 15:29Shifting left with GraphQL tooling
- 16:33Advanced GraphQL tooling examples
- 17:59Closing and Q&A
related talks
06mGraphQL tooling in Rust
27mThe ultimate GraphQL client development experience
35mGraphQL in real life
58mGraphQL -- Flexible APIs for Adaptive Clients
32mTesting GraphQL APIs
57mGraphQL — Closing a Profitable Contract Between Server and Client
19mFunctional Testing of GraphQL APIs: Simple Checks That Catch Real Bugs
31mTeaching GraphQL to write code for you, your users & customers