Join the discussion on Telegram
Why this matters
backend/tsconfig.json lists several stricter checks but has them commented out:
The team clearly considered them. Enabling at least noImplicitReturns, noUnusedLocals, and noFallthroughCasesInSwitch is cheap and would catch real backend regressions (e.g. controller paths that don't return, dead vars in claimable.service.ts already partially flagged by #547).
Acceptance criteria
Optional in the same PR (or follow-up):
Files to touch
Out of scope
- Frontend tsconfig (separate issue)
Join the discussion on Telegram
Why this matters
backend/tsconfig.jsonlists several stricter checks but has them commented out:The team clearly considered them. Enabling at least
noImplicitReturns,noUnusedLocals, andnoFallthroughCasesInSwitchis cheap and would catch real backend regressions (e.g. controller paths that don't return, dead vars inclaimable.service.tsalready partially flagged by #547).Acceptance criteria
noImplicitReturns,noUnusedLocals,noFallthroughCasesInSwitch_varfor params we genuinely don't want, or delete dead code)npm run buildandnpm testpassOptional in the same PR (or follow-up):
noUnusedParametersnoPropertyAccessFromIndexSignatureFiles to touch
backend/tsconfig.jsonOut of scope