marketing-shibata50/multica
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

refactor: remove acceptance_criteria and context_refs from issues

Browse source 
These fields were unused in practice. Removed from frontend types,
issue detail UI, backend handlers, daemon prompt/context, protocol
messages, SQL queries, and tests. DB columns retained with defaults.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Naiyuan Qing 2026-03-26 19:24:34 +08:00
parent 4052017c7a
commit a500001093
17 changed files with 77 additions and 382 deletions
Download patch file Download diff file Expand all files Collapse all files

7
server/pkg/db/queries/issue.sql
View file

@ -15,10 +15,9 @@ WHERE id = $1;
INSERT INTO issue (
workspace_id, title, description, status, priority,
assignee_type, assignee_id, creator_type, creator_id,
parent_issue_id, acceptance_criteria, context_refs,
position, due_date
parent_issue_id, position, due_date
) VALUES (
$1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14
$1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12
) RETURNING *;
-- name: UpdateIssue :one
@ -31,8 +30,6 @@ UPDATE issue SET
assignee_id = sqlc.narg('assignee_id'),
position = COALESCE(sqlc.narg('position'), position),
due_date = sqlc.narg('due_date'),
acceptance_criteria = COALESCE(sqlc.narg('acceptance_criteria'), acceptance_criteria),
context_refs = COALESCE(sqlc.narg('context_refs'), context_refs),
updated_at = now()
WHERE id = $1
RETURNING *;