2 Commits

Include renames

Author	SHA1	Message	Date
tomdebone	43fc889d47	tauri-app: settings view + profile polish ... - App.svelte: new 'settings' view with account/actions/about sections, sign-out button, pdsBase()/appviewBase() helpers, showError wired into logout, profile gains open-in-browser + sign-out + recent-posts heading - NavRail: add settings item + gear icon, View union extended to 5 - tests: NavRail.test.ts now expects 5 buttons + covers settings click, NavRailHarness View type extended	2026-07-07 18:52:10 +02:00
tomdebone	1c75d56134	fix(tauri-app): NavRail click → view switch via callback prop ... 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.	2026-07-06 22:59:29 +02:00