refactor: move category data behind server ownership #360

Closed
opened 2026-05-11 21:02:05 +00:00 by barrettruth · 0 comments
Owner

Parent: #355

Problem

Category reads are partly centralized, but category color writes and category listing still live directly in server actions/routes. That leaves category persistence split across route adapters and core helpers.

Solution

Move category data operations behind one core/server owner:

  • add explicit helpers for setting/removing category colors
  • centralize category listing with counts/colors
  • keep route and action response shapes unchanged
  • add focused tests for category persistence behavior

Acceptance criteria

  • Route/action files no longer hand-roll category DB updates or category-list SQL.
  • Existing UI behavior and API response shape are preserved.
  • Tests cover category color set/remove and category listing.
Parent: #355 ## Problem Category reads are partly centralized, but category color writes and category listing still live directly in server actions/routes. That leaves category persistence split across route adapters and core helpers. ## Solution Move category data operations behind one core/server owner: - add explicit helpers for setting/removing category colors - centralize category listing with counts/colors - keep route and action response shapes unchanged - add focused tests for category persistence behavior ## Acceptance criteria - Route/action files no longer hand-roll category DB updates or category-list SQL. - Existing UI behavior and API response shape are preserved. - Tests cover category color set/remove and category listing.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
barrettruth/delta#360
No description provided.