build: let tsc find the bindings nothing reads
This project has no linter and does not want one, but `strict` says nothing about a binding that is simply never read — and that is the one kind of dead code a reader cannot tell apart from a deliberate seam. `tsc` already walks every file, so it may as well answer the question. Three had accumulated: an unread `type View` import in App, and a `useGameMeta()` resolver in Controls and YourOwn, both of which draw their colours from somewhere else — the game-order list has its own resolver, and YourOwn reads the reader's own records directly. None of them were wrong, they were just leftovers that read as intent. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
This commit is contained in:
co-authored by
Claude Opus 5
parent
5ae559de97
commit
447ea25632
+1
-1
@@ -17,7 +17,7 @@ import { useAppUpdate } from "./state/useAppUpdate.ts";
|
||||
import { useMarkSet } from "./state/useMarkSet.ts";
|
||||
import { useProgress } from "./state/useProgress.ts";
|
||||
import { useDailyLog, type DailyLogMap } from "./state/useDailyLog.ts";
|
||||
import { adoptNewLanes, usePrefs, type View } from "./state/usePrefs.ts";
|
||||
import { adoptNewLanes, usePrefs } from "./state/usePrefs.ts";
|
||||
import { snapDayWidth } from "./state/zoom.ts";
|
||||
import { useCustom } from "./state/useCustom.ts";
|
||||
import { compareRows, SORT_MODES, type Activity, type SortMode } from "./state/sort.ts";
|
||||
|
||||
Reference in New Issue
Block a user