docs: convention for Svelte 5 test fixtures (reactive prop drivers) #637
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
PR #629 introduced
MentionDropdown.test-fixture.svelte— a tiny host component that exposes setters for reactive props so tests can drive prop changes that Svelte 5'smount()API can't natively support (sincemountreturns no settable prop accessors).Markus (#10959) and Felix (#10968) raised this as an undocumented pattern that should be written down before a second instance appears outside
frontend/src/lib/shared/discussion/.Required
X.test-fixture.sveltenext toX.svelte), how to expose a setter viaonReady, when to prefer fixture overrerender().frontend/CLAUDE.mdtesting section, or add a short README underfrontend/src/lib/__test-fixtures__/if a shared folder makes sense..test-fixture.sveltefrom non-test code.Acceptance