refactor: tighten task API route adapters #364

New issue

Closed

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

barrettruth commented

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

Owner

Parent: #355

Problem

Task API routes still repeat ID conversion, owned-task lookup, mutation error mapping, JSON body handling, and dependency validation around the newer task mutation boundary.

Solution

Add route adapter helpers without changing mutation behavior:

centralize task ID parsing and not-found/unauthorized responses
centralize TaskMutationError response mapping
reduce dependency-route body parsing duplication
keep existing status codes and JSON shapes stable

Acceptance criteria

Task route files are thinner adapters over server mutation helpers.
API route validation tests preserve current response contracts.
No task mutation semantics change.

Parent: #355 ## Problem Task API routes still repeat ID conversion, owned-task lookup, mutation error mapping, JSON body handling, and dependency validation around the newer task mutation boundary. ## Solution Add route adapter helpers without changing mutation behavior: - centralize task ID parsing and not-found/unauthorized responses - centralize `TaskMutationError` response mapping - reduce dependency-route body parsing duplication - keep existing status codes and JSON shapes stable ## Acceptance criteria - Task route files are thinner adapters over server mutation helpers. - API route validation tests preserve current response contracts. - No task mutation semantics change.

barrettruth added the

track:api

type:cleanup

labels

2026-05-11 21:02:06 +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:25:04 +00:00

refactor: tighten task API route adapters #379

barrettruth closed this issue