refactor: centralize dashboard server data loaders #319
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
status:blocked
track:api
track:auto
track:core
track:deploy
track:infra
track:ui
type:cleanup
type:docs
type:epic
type:release
type:research
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
barrettruth/delta#319
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Parent: #305
Problem
Dashboard route components fetch task, category, color, settings, and view data directly. As Google sync and self-hosting behavior land, route-level fetching will get harder to reason about unless the server data boundary is explicit.
Solution
Add a server-only dashboard data module:
src/core/*; the loader should coordinate route needs, not become the task domainAcceptance criteria
next buildstill treats authenticated dashboard routes as dynamic.