Tag
schema
Published articles tagged schema.
Evolving a GraphQL schema
GraphQL favors continuous schema evolution over versioned URLs. This chapter classifies safe and breaking changes, documents @deprecated fields and enum values, outlines a deprecation workflow, and shows deprecationReason in NestJS code-first schemas.
Input types and arguments
Arguments tune individual fields; input object types bundle structured write payloads. GraphQL keeps input and output types separate, which shapes how you design mutations, validate data, and avoid breaking clients when forms evolve.
Managing GraphQL schemas in organizations
Large companies rarely expose one undifferentiated graph. This overview covers public, partner, and internal APIs, schema registries and contracts, CI checks against real operations, ownership, and versioning strategies from continuous evolution to dated releases.
Object types and scalars
Object types model entities with fields; scalars are the leaves that hold concrete values. This chapter covers built-in and custom scalars, enums, lists and non-null markers, interfaces, unions, and the __typename field clients use for polymorphism.
Pitfalls when updating a GraphQL backend
Schema changes that look safe on paper still break mobile clients, caches, and federation. This troubleshooting guide lists common symptoms, root causes, and fixes—from nullability shifts to persisted queries and deploy order.
Schema design in GraphQL
Good GraphQL schemas mirror how clients use data, not how tables are joined. This chapter covers query-driven design, naming and nullability, Relay-style connections, mutation payloads, and modeling errors as typed results versus the top-level errors array.
Schemas and SDL
A GraphQL schema is the contract between client and server: types, fields, and root operations written in Schema Definition Language or generated from code. This chapter explains SDL syntax, the Query/Mutation/Subscription roots, schema-first versus code-first workflows, and introspection.