refactor: extract shared client task operations #347
No reviewers
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 milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
barrettruth/delta!347
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-322-client-task-operations"
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?
Problem
Queue, kanban, and calendar each carried their own complete/delete/status-change wiring, including undo payload construction, recurrence-delete prompting, and panel-closing behavior. The unused legacy TaskList path also kept a second copy of those flows alive.
Solution
useTaskOperationsfor client complete/delete/status-change flows.TaskListcomponent.Verification
nix develop --command pnpm vitest run tests/lib/task-operations.test.ts --reporter=verbosenix develop --command just lintnix develop --command just testnix develop --command just buildnix develop --command just ciCloses #322