refactor: centralize task filter parsing #361

New issue

Closed

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

barrettruth commented

2026-05-11 21:02:05 +00:00

Owner

Parent: #355

Problem

Task filter construction is duplicated across dashboard data loading, task API listing, and iCal export. Status, date, sort, and default filters are loosely cast in multiple places.

Solution

Introduce a shared task-filter parser/normalizer:

parse status lists, date aliases, sort fields, and defaults in one module
keep existing behavior unless tests explicitly pin a better validation response
route dashboard, task API, and iCal export through the shared parser

Acceptance criteria

Dashboard, /api/tasks, and iCal export use the same filter contract.
Existing filter behavior is preserved and tested.
Invalid or unknown values are handled consistently.

Parent: #355 ## Problem Task filter construction is duplicated across dashboard data loading, task API listing, and iCal export. Status, date, sort, and default filters are loosely cast in multiple places. ## Solution Introduce a shared task-filter parser/normalizer: - parse status lists, date aliases, sort fields, and defaults in one module - keep existing behavior unless tests explicitly pin a better validation response - route dashboard, task API, and iCal export through the shared parser ## Acceptance criteria - Dashboard, `/api/tasks`, and iCal export use the same filter contract. - Existing filter behavior is preserved and tested. - Invalid or unknown values are handled consistently.

barrettruth added the

track:api

track:core

type:cleanup

labels

2026-05-11 21:02:05 +00:00

barrettruth referenced this issue

2026-05-11 21:02:45 +00:00

tracker: foundation hardening before Google sync #355

barrettruth referenced this issue from a pull request that will close it,

2026-05-11 21:17:49 +00:00

refactor: centralize task filter parsing #377