Shared Schema Policies and Automatic Standards Across Your Company’s Teams
summary
Shows how to enforce concrete schema rules company-wide using GraphQL ESLint and a schema registry like GraphQL Hive. Demonstrates runnable policies that check naming conventions, require descriptions, demand a reason on @deprecated, validate Relay connection/Edge/pageInfo shapes, and apply fixes or suggestions in editors. Explains creating custom rules, running lint in Node or browser, and gating changes in Hive so violations surface as warnings or errors during CI. Relay spec rules
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:11Why schema policies
- 3:06GraphQL ESLint overview
- 5:17Demo in VS Code
- 6:10Schema policy rules
- 8:39Relay spec validation
- 10:04GraphQL Hive integration
- 11:08Schema policies in Hive
related talks
33mEvolving GraphQL Schemas
01mLearn about Schema Design
32mIn-House Schema Registry - The Good the Bad and the Ugly
27mWhat if ... How to Achieve GraphQL Domination
35mGraphQL Docs: Beyond the Schema
49mGraphQL Schema Design — Building Schemas Correctly (version 2)
29mSchemas: The Key To Data Happiness
27mHow The Guild is using GraphQL at scale