apply_changes: unify the mutation tool with assign + milestone (#24)
The write path handled only the est/* and p/* label axes. Extend it to the two
mutations dogfooding proved were missing — assignee and milestone — behind one
unified change model:
- IssueChange gains `assign` and `remilestone` kinds. `planIssueChange` is now
typed to LabelChange (the label kinds only); `isLabelChange` narrows, and a new
pure `summarizeChange(change, currentLabels?)` gives one confirm line for ANY
kind (label kinds delegate to describeChange; field writes describe directly).
- GiteaClient gains `setIssueAssignees` / `setIssueMilestone` (PATCH /issues/{n},
returning the updated issue; milestone 0 clears).
- The main `gitea:applyChange` handler branches: label swaps resolve ids +
setIssueLabels as before; field writes call the new client methods. Snapshot
invalidated either way so board + forecast catch up. ApplyChangeResult.plan is
now optional (absent for field writes).
- issue-screen uses summarizeChange for its diff preview.
Tests: +5 covering isLabelChange, and summarizeChange for assign/unassign,
milestone set-by-title / by-id / removal, and label delegation. Full core suite
132 green; core + desktop typecheck clean.
Follow-up (rest of #24): surface assignee/milestone pickers in the Adjust dialog
and extend the agent's propose_change tool so Reginald can propose them too.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -1,6 +1,13 @@
|
||||
import { describe, expect, it } from 'vitest'
|
||||
|
||||
import { describeChange, type IssueChange, planIssueChange, proposalsFor } from './apply-changes-v0.js'
|
||||
import {
|
||||
describeChange,
|
||||
isLabelChange,
|
||||
type IssueChange,
|
||||
planIssueChange,
|
||||
proposalsFor,
|
||||
summarizeChange,
|
||||
} from './apply-changes-v0.js'
|
||||
|
||||
describe('planIssueChange', () => {
|
||||
it('swaps the estimate label, keeping non-axis labels', () => {
|
||||
@@ -77,3 +84,31 @@ describe('proposalsFor', () => {
|
||||
expect(proposalsFor({ issue: 2 }, ['est/2d'])).toEqual([])
|
||||
})
|
||||
})
|
||||
|
||||
describe('unified change model (assign + milestone)', () => {
|
||||
it('isLabelChange narrows label kinds only', () => {
|
||||
expect(isLabelChange({ kind: 'reestimate', issue: 1, estimate: 'est/2d' })).toBe(true)
|
||||
expect(isLabelChange({ kind: 'reprioritize', issue: 1, priority: 'p/1' })).toBe(true)
|
||||
expect(isLabelChange({ kind: 'assign', issue: 1, assignee: 'christian' })).toBe(false)
|
||||
expect(isLabelChange({ kind: 'remilestone', issue: 1, milestone: 3 })).toBe(false)
|
||||
})
|
||||
|
||||
it('summarizeChange describes an assignment and an unassignment', () => {
|
||||
expect(summarizeChange({ kind: 'assign', issue: 1, assignee: 'christian' })).toBe('assign → @christian')
|
||||
expect(summarizeChange({ kind: 'assign', issue: 1, assignee: null })).toBe('unassign')
|
||||
})
|
||||
|
||||
it('summarizeChange describes a milestone set (by title) and removal', () => {
|
||||
expect(summarizeChange({ kind: 'remilestone', issue: 1, milestone: 3, milestoneTitle: 'P5 — Dogfood' })).toBe(
|
||||
'milestone → P5 — Dogfood',
|
||||
)
|
||||
expect(summarizeChange({ kind: 'remilestone', issue: 1, milestone: 3 })).toBe('milestone → #3')
|
||||
expect(summarizeChange({ kind: 'remilestone', issue: 1, milestone: null })).toBe('remove from milestone')
|
||||
})
|
||||
|
||||
it('summarizeChange delegates label kinds to describeChange (needs current labels)', () => {
|
||||
const change: IssueChange = { kind: 'reestimate', issue: 1, estimate: 'est/5d' }
|
||||
expect(summarizeChange(change, ['est/2d'])).toBe('est/2d → est/5d')
|
||||
expect(summarizeChange(change, ['est/5d'])).toBe('no change')
|
||||
})
|
||||
})
|
||||
|
||||
@@ -17,6 +17,15 @@ import {
|
||||
export type IssueChange =
|
||||
| { kind: 'reestimate'; issue: number; estimate: EstimateLabel | null }
|
||||
| { kind: 'reprioritize'; issue: number; priority: PriorityLabel | null }
|
||||
| { kind: 'assign'; issue: number; assignee: string | null }
|
||||
| { kind: 'remilestone'; issue: number; milestone: number | null; milestoneTitle?: string | null }
|
||||
|
||||
/** The label axes are the only kinds planned as a label swap; the rest are field writes. */
|
||||
export function isLabelChange(
|
||||
change: IssueChange,
|
||||
): change is Extract<IssueChange, { kind: 'reestimate' | 'reprioritize' }> {
|
||||
return change.kind === 'reestimate' || change.kind === 'reprioritize'
|
||||
}
|
||||
|
||||
export interface LabelPlan {
|
||||
/** The full resulting label-name set (order: kept labels, then the new axis label). */
|
||||
@@ -29,7 +38,10 @@ export interface LabelPlan {
|
||||
noop: boolean
|
||||
}
|
||||
|
||||
function axisFor(change: IssueChange): { labels: readonly string[]; target: string | null } {
|
||||
/** A change that resolves to a label swap (the only kind `planIssueChange` accepts). */
|
||||
export type LabelChange = Extract<IssueChange, { kind: 'reestimate' | 'reprioritize' }>
|
||||
|
||||
function axisFor(change: LabelChange): { labels: readonly string[]; target: string | null } {
|
||||
return change.kind === 'reestimate'
|
||||
? { labels: ESTIMATE_LABELS, target: change.estimate }
|
||||
: { labels: PRIORITY_LABELS, target: change.priority }
|
||||
@@ -40,7 +52,7 @@ function axisFor(change: IssueChange): { labels: readonly string[]; target: stri
|
||||
* change's axis except the target, adds the target if absent. Setting the axis
|
||||
* to null clears it. Cleans up a duplicated axis (two `est/*`) as a side effect.
|
||||
*/
|
||||
export function planIssueChange(current: string[], change: IssueChange): LabelPlan {
|
||||
export function planIssueChange(current: string[], change: LabelChange): LabelPlan {
|
||||
const { labels: axis, target } = axisFor(change)
|
||||
const onAxis = current.filter((l) => axis.includes(l))
|
||||
const removed = onAxis.filter((l) => l !== target)
|
||||
@@ -58,6 +70,26 @@ export function describeChange(plan: LabelPlan): string {
|
||||
return `${from} → ${to}`
|
||||
}
|
||||
|
||||
/**
|
||||
* One human-readable confirm line for ANY change kind — the unified describe for
|
||||
* the propose-approve UI. Label kinds delegate to {@link describeChange} (so they
|
||||
* need the issue's current labels); assign/milestone describe the field write
|
||||
* directly. Pure; no network.
|
||||
*/
|
||||
export function summarizeChange(change: IssueChange, currentLabels: string[] = []): string {
|
||||
switch (change.kind) {
|
||||
case 'reestimate':
|
||||
case 'reprioritize':
|
||||
return describeChange(planIssueChange(currentLabels, change))
|
||||
case 'assign':
|
||||
return change.assignee ? `assign → @${change.assignee}` : 'unassign'
|
||||
case 'remilestone':
|
||||
return change.milestone == null
|
||||
? 'remove from milestone'
|
||||
: `milestone → ${change.milestoneTitle ?? `#${change.milestone}`}`
|
||||
}
|
||||
}
|
||||
|
||||
/** A change the agent proposes: the concrete op + its diff, ready for approve-then-apply. */
|
||||
export interface ChangeProposal {
|
||||
change: IssueChange
|
||||
|
||||
Reference in New Issue
Block a user