tomdebone
1c75d56134
The `bind:current={view}` pattern in NavRail did not propagate
clicks to the parent's $state. Svelte 5's $bindable on this
runtime is flakey and on this particular build (Tauri 2.11 +
svelte 5.x) the setter was never invoked when a button was
clicked, so the view state stayed 'home' no matter which rail
button the user pressed. The user reported 'search tut sich nix
genau auch bei compose etc.'
Replace with explicit callback prop:
let { view = 'home', on_select } = $props();
onclick={() => on_select?.(item.id)}
The parent then mutates its own `view` rune directly via the
arrow function — Svelte tracks this unconditionally regardless of
runtime-specific bindable semantics.
Includes a vitest regression test that mounts a real Svelte
component harness (jsdom) and asserts that click events on each
rail button flip the parent's `view` and update the .active
class — so any future regression is caught in CI rather than at
the Tauri app window.
35 lines
863 B
JSON
35 lines
863 B
JSON
{
|
|
"name": "maarcadetweet-app",
|
|
"private": true,
|
|
"version": "0.1.0",
|
|
"type": "module",
|
|
"scripts": {
|
|
"dev": "vite",
|
|
"build": "vite build",
|
|
"preview": "vite preview",
|
|
"check": "svelte-check --tsconfig ./tsconfig.json",
|
|
"test": "vitest run",
|
|
"test:watch": "vitest",
|
|
"tauri": "tauri"
|
|
},
|
|
"packageManager": "npm@10.8.2",
|
|
"dependencies": {
|
|
"@tauri-apps/api": "^2.1.1",
|
|
"@tauri-apps/plugin-dialog": "^2.0.1",
|
|
"@tauri-apps/plugin-notification": "^2.0.1"
|
|
},
|
|
"devDependencies": {
|
|
"@sveltejs/vite-plugin-svelte": "^4.0.2",
|
|
"@tauri-apps/cli": "^2.1.0",
|
|
"@tsconfig/svelte": "^5.0.4",
|
|
"jsdom": "^29.1.1",
|
|
"svelte": "^5.2.0",
|
|
"svelte-check": "^4.1.0",
|
|
"tslib": "^2.8.0",
|
|
"typescript": "^5.6.3",
|
|
"vite": "^5.4.10",
|
|
"vite-plugin-static-copy": "^1.0.6",
|
|
"vitest": "^2.1.0"
|
|
}
|
|
}
|