fix(ci): 라우트 수와 상관없이 라우트 런타임 음성 fixture 진단을 고정한다

샘플 라우트를 지워 라우트가 3개가 되자 FE-GATE-003의 route-runtime 음성 fixture가
TS2740 대신 TS2739를 내 기대 진단과 어긋났다. tsc는 빠진 키가 많으면 TS2740,
적으면 TS2739를 낸다. fixture가 정확히 한 라우트만 빼도록 바꿔 어느 라우트 수에서나
TS2741이 나오게 하고 기대 진단을 맞췄다.
This commit is contained in:
DongHyeonka
2026-11-08 14:37:40 +09:00
parent 4e885c1d04
commit e47a0ab23d
2 changed files with 7 additions and 4 deletions
+1 -1
View File
@@ -144,7 +144,7 @@
"script": "check:types:fixture:route-runtime",
"expect": "fail",
"expectedExitCode": 1,
"expectedDiagnosticId": "error TS2740:"
"expectedDiagnosticId": "error TS2741:"
},
{
"id": "check-types-fixture-page-action",
+6 -3
View File
@@ -2,9 +2,12 @@ import { ROUTE_RUNTIME_CONTRACT } from "../../../src/features/installed-feature-
type RouteId = keyof typeof ROUTE_RUNTIME_CONTRACT;
export const missingRuntime = {
APP_HOME: true,
} satisfies Record<RouteId, boolean>;
// 2026-11-07. Exactly one route is left out. tsc names a short list of
// missing keys (TS2739) and a long one with "and N more" (TS2740), so an
// object that kept one route changed its diagnostic when the template's
// sample routes were deleted. One missing key is TS2741 at any route count.
declare const withoutHome: Omit<Record<RouteId, boolean>, "APP_HOME">;
export const missingRuntime: Record<RouteId, boolean> = withoutHome;
export const orphanRuntime = {
...Object.fromEntries(