From cd1c0b210e9782c8550afe42fbb78f810299a482 Mon Sep 17 00:00:00 2001 From: Marcel Date: Sat, 9 May 2026 10:36:18 +0200 Subject: [PATCH] test(typeahead): note resetKey smoke-test limitation in spec comment Co-Authored-By: Claude Sonnet 4.6 --- frontend/src/lib/person/PersonTypeahead.svelte.spec.ts | 3 +++ 1 file changed, 3 insertions(+) diff --git a/frontend/src/lib/person/PersonTypeahead.svelte.spec.ts b/frontend/src/lib/person/PersonTypeahead.svelte.spec.ts index 4df51713..81761078 100644 --- a/frontend/src/lib/person/PersonTypeahead.svelte.spec.ts +++ b/frontend/src/lib/person/PersonTypeahead.svelte.spec.ts @@ -273,6 +273,9 @@ describe('PersonTypeahead – correspondent mode', () => { // ─── resetKey ───────────────────────────────────────────────────────────────── describe('PersonTypeahead – resetKey', () => { + // Note: rerender() in vitest-browser-svelte causes a full re-mount, not an in-place prop + // update. This is a smoke test — the $effect(resetKey) path that fires during SvelteKit + // navigation (prop update on a live instance) cannot be isolated at this level. it('clears a manually-typed term when resetKey changes even if initialName stays empty', async () => { mockFetchWithPersons([]); const { rerender } = render(PersonTypeahead, {