Lightning Talk: The @deprecated Journey: Five Stops From Schema Hint To Gateway Power
summary
Shows a concrete path that turns @deprecated into governance and runtime tooling: add replacedBy/migrationURL and sunset date args, run a schema transformer that returns fields but adds extension warnings, log hits and errors for post-sunset requests, and capture client identity via GraphQL context so observability is client-aware telemetry. A registry plus agents then scan usage, open PRs to migrate or prune after ~2 weeks of inactivity, making deprecation actionable, automatable, and enforceable.
AI-written summary · about
related talks
47mPanel - Modernization Stories - Monoliths, Migrations and Mergers
45mHitchhiker’s Guide for Software Architects: Legacy Migration
36mThe State Management Rollercoaster
01h 01mLegacy Architecture Migration Patterns with DDD
30mA Tale of Two Codepaths: Notes on a Refactor
02h 28mWorkshop 2
06mLightning talk from Darpan Kakadia
01mThe Path Through Legacy: Delicate Balance Between Tolerance and Phobia