lint: type-checked eslint rules #7

Sammanfogat

supernaut sammanfogade 1 incheckning från lint/type-checked in i main

2026-07-29 20:12:57 +00:00

supernaut kommenterad

2026-07-29 20:09:43 +00:00

Ägare

Enables typescript-eslint's recommendedTypeChecked (#59), for parity with the sibling service repos.

This repo was already clean — zero findings. That is a genuine result rather than a non-event: the
rules that fired elsewhere (no-unsafe-enum-comparison on bitborg-payment's refund path,
require-await across bitborg-auth-reconciler's test fakes) found nothing to complain about here, so
the config lands with no code changes at all.

Included anyway so the three service repos share one lint baseline. Otherwise the next module added
here would be the first to be type-checked, and would arrive with a backlog attached.

parserOptions.projectService with allowDefaultProject for the root config files (*.mjs,
vitest.config.ts), which otherwise fail to parse rather than being linted

Why `recommendedTypeChecked` and not `strictTypeChecked`

The stricter tier is declared non-stable upstream, and its no-unnecessary-condition rule fires on
exactly the defensive guards that protect untrusted runtime data. Not worth the false-positive tax.

Refs #59

Enables typescript-eslint's `recommendedTypeChecked` (#59), for parity with the sibling service repos. **This repo was already clean** — zero findings. That is a genuine result rather than a non-event: the rules that fired elsewhere (`no-unsafe-enum-comparison` on bitborg-payment's refund path, `require-await` across bitborg-auth-reconciler's test fakes) found nothing to complain about here, so the config lands with no code changes at all. Included anyway so the three service repos share one lint baseline. Otherwise the next module added here would be the first to be type-checked, and would arrive with a backlog attached. - `parserOptions.projectService` with `allowDefaultProject` for the root config files (`*.mjs`, `vitest.config.ts`), which otherwise fail to parse rather than being linted ## Why `recommendedTypeChecked` and not `strictTypeChecked` The stricter tier is declared non-stable upstream, and its `no-unnecessary-condition` rule fires on exactly the defensive guards that protect untrusted runtime data. Not worth the false-positive tax. Refs #59

supernaut lade till 1 incheckning

2026-07-29 20:09:43 +00:00