test/hookable.test.ts (1)

315-318: Add a parity test for HookableCore.clearHook as well.

Line 315 validates non-existent hook safety on Hookable, but the same new API was also added to HookableCore. A small parity test would prevent regressions in that path.

Proposed test addition

 describe("HookableCore", () => {
   test("basic functionality", async () => {
@@
     expect(obj.called).toBe(true);
   });
+
+  test("clearHook removes only the target hook handlers", async () => {
+    const hookable = new HookableCore<{ a(): void; b(): void }>();
+    const a = vi.fn();
+    const b = vi.fn();
+
+    hookable.hook("a", a);
+    hookable.hook("a", a);
+    hookable.hook("b", b);
+
+    hookable.clearHook("a");
+
+    await hookable.callHook("a");
+    await hookable.callHook("b");
+
+    expect(a).toBeCalledTimes(0);
+    expect(b).toBeCalledTimes(1);
+  });
 });

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@test/hookable.test.ts` around lines 315 - 318, Add a parity test for
HookableCore.clearHook mirroring the existing Hookable test: instantiate
HookableCore, call clearHook("test:nonexistent") and assert it does not throw.
Target the HookableCore class and its clearHook method (HookableCore.clearHook)
so the new test ensures the same non-existent-hook safety behavior as the
Hookable test.