You’re viewing Paradaux’s public workspaceSign in to vote Get taskl.ie for your team

PAR-415

Loading issues

PAR-415 · D2 · Issues writes: create/update/move/archive/bulk as use… · Paradaux · taskl.ie

PAR-415

D2 · Issues writes: create/update/move/archive/bulk as use cases; REST, MCP and Discord adapters call one facade

Domain migration. Depends on D1. Commandments 14–17, 19, 20, 29 and 31.

Backend

Use cases:
- CreateIssue, UpdateIssue (per-field patch), MoveIssue (status / order / team), ArchiveIssue, RestoreIssue and DeleteIssue
- BulkUpdateIssues, the backend half of PAR-365
- AddSubIssue and SetParent
Domain errors: a sealed IssueError.
Facade: TasksFacade write methods, @Transactional.
Adapters, all thin and all calling the same facade methods (rule 15):
- REST: IssueApiController moves to tasks/api.
- MCP: TaskMcpTools and BulkMcpTools move to tasks/mcp.
- Discord: the create-from-thread path in discord/TaskInstructionListener calls TasksFacade.create(...).
Remove the corresponding methods from PostgresTaskSystem. If the class is empty afterwards, delete it.
Events: emit issue_event rows inside the transaction. Discord and GitHub notifications for issue changes go through the outbox (PAR-412).
Remove EventBatch and TenantContext ThreadLocal usage in these paths. Pass RequestContext instead.

Web

Issue mutations use generated-client hooks with optimistic updates. These are the ones PAR-401 builds on.
Remove the server-action and router.refresh() paths for issue edits.

Acceptance

Creating a task from Discord, MCP and the web runs the same CreateIssue use case. Prove it with a test per adapter.
Every test passes, and the ArchUnit store and ESLint suppressions shrink. List both deltas in the PR.

Activity

taskl.ie created the issue 6d ago
taskl.ie set status to In Progress 5d ago
taskl.ie5d ago
Plan (branch par-415-issues-writes from rebuild): add write use cases (Create/Update/Move/Archive/Restore/Delete/BulkUpdate/SetParent) to the issues domain beside the reads, with sealed IssueError and Rollback.onErr on IssuesFacade. Writes persist through JdbcIssueRepository (tenant-scoped); issue_event recording is a small persistence call in the same tx; Discord/GitHub/webhook side effects go via Outbox + handlers. REST write endpoints under /api/public/w/{slug}/issues, MCP write tools in issues/mcp (same names), Discord create/update call the facade. Shrink PostgresTaskSystem and drop ThreadLocal use on these paths. Web: write hooks in domains/issues/data. Ratchet deltas reported in PR.
taskl.ie5d ago
PR open: https://github.com/ParadauxIO/taskl.ie/pull/54
taskl.ie set status to Pending Release 5d ago
taskl.ie5d ago
Merged into rebuild as #54 (99135b8). Create, update, move, archive and bulk changes are use cases behind IssuesFacade. REST, MCP and Discord triage all call the same facade methods, and a test drives all three. Activity is now delivered through the outbox (issue.activity) in the same transaction, and EventBatch is deleted.

Ratchet: ArchUnit store 1283 → 1016 distinct violations (line numbers stripped). ESLint suppressions unchanged at 61.

Accepted exception: about 10 genuinely new cross-domain entries in legacy adapters that now call the new facade:
- TaskInstructionListener → TaskSystem.defaultWorkspaceId
- TriageService → IssueError / TaskModels.Task
- GithubWebhookService → TaskModels.Task.ref
These classes are rewritten by PAR-420 (Discord and triage) and PAR-421 (GitHub), and those tickets must remove these entries.

Behaviour changes:
- Unknown or foreign ids return 400 instead of being silently dropped.
- Titles are validated.
- Create returns 201.
- The outbox worker runs in the worker or all role (production runs all).
V40__issue_event_outboxed is now taken; PAR-418 renumbers.
taskl.ie changed status from Pending release to Done 5d ago

Workspace permission required to comment

Comments and reactions require workspace permission. Ask a workspace owner or admin for access. You can sign in to vote.