fix: add explicit types to implicit any params in server spec

[nicknisi]

Summary

• Adds unknown[] type annotations to 6 args parameters in consoleErrorSpy.mock.calls.filter() callbacks
• Fixes noImplicitAny errors from pnpm typecheck

Test plan

• pnpm typecheck passes

---

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[greptile-apps]

Greptile Summary

This PR adds explicit unknown[] type annotations to 6 args parameters in consoleErrorSpy.mock.calls.filter() callbacks inside src/server/server.spec.ts, resolving noImplicitAny TypeScript errors surfaced by pnpm typecheck. The use of unknown[] is appropriate and slightly safer than any[] as it enforces proper type narrowing through the existing typeof args[0] === 'string' guards before calling .includes().

Confidence Score: 5/5

Safe to merge — minimal, mechanical TypeScript annotation fix in a test file with no logic changes.

All 6 changes are identical: adding unknown[] type annotations to filter callback parameters. No runtime behaviour is altered, and the type choice is correct given the existing narrowing guards.

No files require special attention.

Important Files Changed

Filename	Overview
src/server/server.spec.ts	Adds explicit unknown[] type annotations to 6 args parameters in consoleErrorSpy.mock.calls.filter() callbacks to resolve noImplicitAny TypeScript errors. No logic changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["consoleErrorSpy.mock.calls\n(MockInstance call log)"] --> B["filter((args: unknown[]) => ...)"]
    B --> C{"typeof args[0] === 'string'?"}
    C -- Yes --> D{"args[0].includes(message)?"}
    C -- No --> E["Exclude call"]
    D -- Yes --> F["Include call in filtered results"]
    D -- No --> E

Loading

_{Reviews (1): Last reviewed commit: "fix: add explicit types to implicit `any..." | Re-trigger Greptile}