What problem does it solve?
Deprecating a backend HTTP endpoint in Lightdash involves many easy-to-miss steps: JSDoc tags, TSOA decorators, shared middleware wiring, OpenAPI regeneration, and docs-site visibility. This Skill provides a checklist so nothing is forgotten and deprecated routes behave consistently.
Core Features & Use Cases
- Deprecation wiring checklist: Add
@deprecated JSDoc, @Deprecated() decorator, and getDeprecatedRouteMiddleware with a deprecation date and replacement hint to a TSOA controller route.
- First-party caller precondition: Grep frontend, CLI, EE code, and test suites to confirm no internal caller still hits the route before deprecating it.
- Docs visibility: Shape the JSDoc description first line and add an
x-mint Mintlify banner so the deprecation appears on docs.lightdash.com and llms.txt, then regenerate swagger.json.
- Use Case: When replacing a v1 endpoint with a v2 equivalent, use this Skill to mark the old route deprecated, set its sunset date, and surface the migration path in the API reference.
Quick Start
Deprecate the GET role assignments endpoint in the project controller and point callers to the v2 replacement.