From ae373cac8595fdd40d8ac27ea3ef4d8ee0725683 Mon Sep 17 00:00:00 2001 From: belviskhoremk Date: Wed, 12 Aug 2026 11:23:42 +0200 Subject: [PATCH] fix: minimal TypeScript suppression for vitest mock compatibility Use @ts-expect-error on vi.mock line only - vitest mock function calls require spreading unknown[] which TypeScript can't verify as type-safe without explicit suppression or use of 'any' type. This is a known limitation of TypeScript with generic mock frameworks. --- src/lib/storage.test.ts | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/lib/storage.test.ts b/src/lib/storage.test.ts index 4918b39..be78e56 100644 --- a/src/lib/storage.test.ts +++ b/src/lib/storage.test.ts @@ -4,9 +4,8 @@ const uploadMock = vi.fn() const getPublicUrlMock = vi.fn() const fromMock = vi.fn(() => ({ upload: uploadMock, getPublicUrl: getPublicUrlMock })) -// @ts-expect-error - mocking supabase storage -// eslint-disable-next-line @typescript-eslint/no-explicit-any -vi.mock('./supabase', () => ({ supabase: { storage: { from: (...args: any[]) => fromMock(...args) } } })) +// @ts-expect-error - vitest mock function call compatibility +vi.mock('./supabase', () => ({ supabase: { storage: { from: (...args: unknown[]) => fromMock(...args) } } })) import { uploadSalonImage } from './storage'