Schema Evolution with @deprecated
GraphQL APIs evolve without version numbers: additive changes are always safe, and removals happen by marking fields `@deprecated(reason:)`, watching per-field usage telemetry until traffic hits zero, then deleting. The client-specified selection set is what makes per-field usage measurable at all.
This Concept is waiting for its first lesson!
GraphQL APIs evolve without version numbers: additive changes are always safe, and removals happen by marking fields `@deprecated(reason:)`, watching per-field usage telemetry until traffic hits zero, then deleting. The client-specified selection set is what makes per-field usage measurable at all.
Are you a teacher? Sign in to start contributing.
Sign In