[tasks] persist filter state on back navigation

[capcom6]

Problem

Task list filters (statuses, priorities, project, sort, pagination) are lost when navigating from a task list to a task detail and back. The filter state was held in local `` variables, which reset on component mount.

Solution

Created a shared Svelte 5 store (stores/task-filters.svelte.ts) that holds filter state in module-level ``, keyed by route path. Each task list page now:

1. Restores filter state from the store on mount (before the load effect runs)
2. Persists filter state to the store via a `` whenever filters change

Files

• New: frontend/src/lib/stores/task-filters.svelte.ts — module-level store keyed by route
• Modified: dashboard-tasks.svelte — key /dashboard/all
• Modified: dashboard-personal.svelte — key /dashboard
• Modified: project-tasks.svelte — per-project key /projects/{slug}

Summary by CodeRabbit

• New Features
  • Dashboard task filters, sorting, and pagination now persist when navigating away and return automatically when revisiting.
  • Personal and “all tasks” dashboards restore the last selected filter and sort settings (including current pagination offset).
  • Project task views now persist and restore filter/sort/search and pagination per project route, resetting the search query when no prior snapshot exists.
  • Filter state is maintained independently for each dashboard and project view.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fe7d362b-2fd5-4f68-a031-b676fbe27da8

📥 Commits

Reviewing files that changed from the base of the PR and between 2110a59 and 00dfc34.

📒 Files selected for processing (1)

• frontend/src/lib/pages/project-tasks.svelte

🚧 Files skipped from review as they are similar to previous changes (1)

• frontend/src/lib/pages/project-tasks.svelte

---

📝 Walkthrough

Walkthrough

Task filter snapshots are stored in memory and keyed by route. Dashboard and project task pages restore saved filter, sorting, and pagination values, then save updated state through reactive effects.

Changes

Task filter persistence

Layer / File(s)	Summary
Snapshot store contract frontend/src/lib/stores/task-filters.svelte.ts	Defines FilterSnapshot and adds path-keyed get, save, and clear operations.
Dashboard state restoration and saving frontend/src/lib/pages/dashboard-personal.svelte, frontend/src/lib/pages/dashboard-tasks.svelte	Dashboard pages restore saved filter and sort values and persist current state under route-specific keys.
Project task state restoration and saving frontend/src/lib/pages/project-tasks.svelte	Project task pages derive a route key, restore saved filter state, and persist changes to filters, sorting, and offset.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Suggested reviewers: dudina-ma

Sequence Diagram(s)

sequenceDiagram
  participant TaskPage
  participant task-filters
  participant SnapshotStore
  TaskPage->>task-filters: getSnapshot(route key)
  task-filters->>SnapshotStore: read FilterSnapshot
  SnapshotStore-->>task-filters: saved state or null
  task-filters-->>TaskPage: restore filter, sort, and offset
  TaskPage->>task-filters: saveSnapshot(route key, current state)
  task-filters->>SnapshotStore: write FilterSnapshot

Loading

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: persisting task filter state when navigating away and back.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🤖 Pull request artifacts

Platform	File
🐳 Docker	GitHub Container Registry
🍎 Darwin arm64	backend_Darwin_arm64.tar.gz
🍎 Darwin x86_64	backend_Darwin_x86_64.tar.gz
🐧 Linux arm64	backend_Linux_arm64.tar.gz
🐧 Linux i386	backend_Linux_i386.tar.gz
🐧 Linux x86_64	backend_Linux_x86_64.tar.gz
🪟 Windows arm64	backend_Windows_arm64.zip
🪟 Windows i386	backend_Windows_i386.zip
🪟 Windows x86_64	backend_Windows_x86_64.zip

[capcom6]

@coderabbitai full review

[coderabbitai]

✅ Action performed

Full review finished.

[capcom6]

@coderabbitai full review

[coderabbitai]

✅ Action performed

Full review finished.

---

Your plan includes PR reviews subject to rate limits. More reviews will be available in 35 minutes.

[capcom6]

@coderabbitai full review

[coderabbitai]

✅ Action performed

Full review finished.

---

Your plan includes PR reviews subject to rate limits. More reviews will be available in 58 minutes.

[coderabbitai]

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@frontend/src/lib/pages/project-tasks.svelte`:
- Around line 97-105: Guard the snapshot-saving $effect around saveSnapshot so
it returns without writing until currentRouteKey is synchronized with routeKey
and the new project’s state has been loaded. Once both keys match, preserve the
existing filterStatuses, filterPriorities, sort, and offset payload and save it
under the stable route key.
- Around line 97-105: Guard the snapshot-saving $effect using currentRouteKey so
it only calls saveSnapshot when currentRouteKey matches the reactive routeKey.
Keep the existing filter, priority, sort, and offset snapshot payload unchanged,
preventing the previous project’s state from being written under the new project
key during navigation.
- Around line 36-43: Wrap the snapshot restoration logic around
getSnapshot(routeKey) in a Svelte 5 $effect so it reruns whenever the dynamic
routeKey changes. Restore all saved state for an existing snapshot, and
explicitly clear searchQuery and sort when no snapshot exists to prevent state
leaking between projects.
- Around line 36-43: Wrap the snapshot restoration logic around routeKey in an
$effect so it re-runs when dynamic route parameters change. When a snapshot
exists, restore its filterStatuses, filterPriorities, sort, and offset; when
none exists, clear searchQuery and sort to prevent state leaking between
projects.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fc4a00a0-9cc5-43f7-ab84-02da16042bf3

📥 Commits

Reviewing files that changed from the base of the PR and between 83faa4c and 2110a59.

📒 Files selected for processing (4)

• frontend/src/lib/pages/dashboard-personal.svelte
• frontend/src/lib/pages/dashboard-tasks.svelte
• frontend/src/lib/pages/project-tasks.svelte
• frontend/src/lib/stores/task-filters.svelte.ts