History

Jacob Schmidt d1e4989303 Add edit/delete buttons to SidePanel for all sections, custom entry filenames, vault persistence

- Add edit/delete icon buttons to SidePanel items for entries, todos, lists, and fragments
- Move fragment edit/delete controls from FragmentEditor main panel to SidePanel
- Add externalEditRequested prop to FragmentEditor for parent-controlled edit mode
- Add fragment delete handling in +page.svelte performDelete flow
- Support custom entry filenames via FileName parameter in EntrySavePayload
- Fix vault persistence for custom-named entries (non-date-formatted .md files)
- Add VaultStorageService SaveCustomEntries helper for _custom_entries.vault
- Add entries.delete backend command and wire through EntryFileService
- Remove Write/Preview toggle from MarkdownEditor (previewOnly controlled by parent)
- Add smoke tests for vault custom entry roundtrip and entry save with custom filename

Co-Authored-By: Oz <oz-agent@warp.dev>

2026-02-26 19:40:43 -06:00

src

Add edit/delete buttons to SidePanel for all sections, custom entry filenames, vault persistence

2026-02-26 19:40:43 -06:00

src-tauri

Lists & todos backend, editor refactor, inline create, UX improvements

2026-02-26 17:33:27 -06:00

static

Refactor journal UI and add markdown editor workflow

2026-02-25 17:52:30 -06:00

.gitignore

Initial Frontend Rework

2026-02-24 22:16:51 -06:00

package-lock.json

Initial Frontend Rework

2026-02-24 22:16:51 -06:00

package.json

Initial Frontend Rework

2026-02-24 22:16:51 -06:00

README.md

Refactor frontend state to store-first architecture

2026-02-25 20:52:46 -06:00

svelte.config.js

Initial Frontend Rework

2026-02-24 22:16:51 -06:00

tsconfig.json

Initial Frontend Rework

2026-02-24 22:16:51 -06:00

vite.config.js

Initial Frontend Rework

2026-02-24 22:16:51 -06:00

README.md

Tauri + SvelteKit + TypeScript

This template should help get you started developing with Tauri, SvelteKit and TypeScript in Vite.

Frontend State Management

This app uses Svelte stores as the source of truth for feature state.

Current Stores

src/lib/stores/entries.ts
- state: entriesStore
- helpers: getDefaultEntry, createEntryDraft
src/lib/stores/fragments.ts
- state: fragmentsStore
- helpers: parse/serialize + fragment CRUD helpers (createFragmentItem, updateFragmentItem, prependFragmentItem, removeFragmentItem)
src/lib/stores/todos.ts
- state: todoListsStore, todosStore
- helpers: parse/serialize + todo list/item CRUD helpers
src/lib/stores/lists.ts
- state: listsStore
- helpers: createListDraft
src/lib/stores/settings.ts
- state: settingsTags, settingsFragmentTypes

Store-First Rule

Components should call store helper functions for CRUD operations.
Components should avoid embedding feature-specific mutation/parsing logic.
UI components should focus on rendering, local form state, and invoking store operations.

What Still Needs Setup

Move settings CRUD helpers into settings.ts (currently add/edit/remove logic lives in routes/settings/+page.svelte).
Add full CRUD helpers for entries and lists stores (update/remove/reorder and optional find-by-id helpers).
Consolidate todo state into a single custom store API (or a single store object) so todoListsStore and todosStore updates are atomic.
Move calendar-created notes into a dedicated calendar store (currently local to SidePanel.svelte).
Add persistence/hydration layer so store state survives app restart and can be synchronized with backend commands.

Suggested Next Refactor

Introduce feature service wrappers per store (for example entriesService, fragmentsService) that handle:
- in-memory store mutation
- backend command call (sendCommand)
- optimistic update / rollback policy
- error normalization for UI

Recommended IDE Setup

VS Code + Svelte + Tauri + rust-analyzer.