Join our community: https://t.me/+DOylgFv1jyJlNzM0
Why this matters
frontend/src/lib/api-types.ts presumably hand-declares TypeScript interfaces mirroring backend API responses. With no generation step from backend/src/config/swagger.ts's OpenAPI spec, a backend field rename or type change (several of which are already tracked as separate backend issues) can silently desync from the frontend's types, producing runtime undefined access bugs that TypeScript won't catch because both sides compile independently.
Acceptance criteria
Files to touch
frontend/src/lib/api-types.ts
backend/src/config/swagger.ts
Out of scope
- Fully automating type generation in CI (can be a stretch goal noted in the issue, not required)
- Rewriting existing API call sites
Why this matters
frontend/src/lib/api-types.tspresumably hand-declares TypeScript interfaces mirroring backend API responses. With no generation step frombackend/src/config/swagger.ts's OpenAPI spec, a backend field rename or type change (several of which are already tracked as separate backend issues) can silently desync from the frontend's types, producing runtimeundefinedaccess bugs that TypeScript won't catch because both sides compile independently.Acceptance criteria
openapi-typescript) fed by the backend's swagger outputapi-types.tsnoting it must be manually kept in sync and where the source of truth livesFiles to touch
frontend/src/lib/api-types.tsbackend/src/config/swagger.tsOut of scope