From e3c097fd441f7a116af79a13f4e95432ff6ff286 Mon Sep 17 00:00:00 2001 From: Peter Todd Date: Fri, 17 Jul 2026 17:19:36 +0100 Subject: [PATCH] core: fix ineffective biome-ignore on ResolverRegistry (unblock lint gate) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The `noExplicitAny` suppression for `ResolverRegistry` was written across two comment lines; the continuation line sits between the `// biome-ignore` directive and the annotated `export type`, so Biome reports the suppression as unused — one error, which fails the `pnpm lint:biome` CI gate (it is clean of prior backlog, so any error is fatal). Collapse it to a single-line biome-ignore, the same form the adjacent `AnyResolveContext` suppression already uses. No behaviour change. Co-Authored-By: Claude Opus 4.8 --- packages/core/src/engine/SpatialEntryStore.ts | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/packages/core/src/engine/SpatialEntryStore.ts b/packages/core/src/engine/SpatialEntryStore.ts index 5806d9b..c2a183b 100644 --- a/packages/core/src/engine/SpatialEntryStore.ts +++ b/packages/core/src/engine/SpatialEntryStore.ts @@ -17,8 +17,7 @@ import type { EntryResources, ResolveContext, ResolveTask, ResourceResolver } fr * special-case a kind here. */ -// biome-ignore lint/suspicious/noExplicitAny: the registry is heterogeneous by design — each -// resolver has its own config and element types, and the store deliberately cannot see them. +// biome-ignore lint/suspicious/noExplicitAny: the registry is heterogeneous by design — each resolver has its own config and element types, and the store deliberately cannot see them. export type ResolverRegistry = Readonly>>; // biome-ignore lint/suspicious/noExplicitAny: see above.