ros/automaker
1
0
Fork 0
mirror of https://github.com/AutoMaker-Org/automaker.git synced 2026-01-31 20:03:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: Invalidate all features query on pipeline_step_started event

Browse Source 
When a pipeline step starts, the feature status changes to the pipeline
column status. Previously, only the single feature query was invalidated,
but the Kanban board uses the all features query for column grouping.

This caused the UI to not immediately reflect features moving to custom
pipeline columns - updates would only appear after the first pipeline
step completed.

Fixes #668

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Shirone
2026-01-24 15:44:39 +01:00
parent d8fa5c4cd1
commit d04934359a
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
apps/ui/src/hooks/use-query-invalidation.ts
View File

@@ -115,13 +115,16 @@ export function useAutoModeQueryInvalidation(projectPath: string | undefined) {
// This allows polling to be disabled when WebSocket events are flowing
recordGlobalEvent();
// Invalidate features when agent completes, errors, or receives plan approval
// Invalidate features when agent completes, errors, receives plan approval, or pipeline step changes
// Note: pipeline_step_started is included to ensure Kanban board immediately reflects
// feature moving to custom pipeline columns (fixes GitHub issue #668)
if (
event.type === 'auto_mode_feature_complete' ||
event.type === 'auto_mode_error' ||
event.type === 'plan_approval_required' ||
event.type === 'plan_approved' ||
event.type === 'plan_rejected' ||
event.type === 'pipeline_step_started' ||
event.type === 'pipeline_step_complete'
) {
queryClient.invalidateQueries({
@@ -142,11 +145,12 @@ export function useAutoModeQueryInvalidation(projectPath: string | undefined) {
}
// Invalidate specific feature when it starts or has phase changes
// Note: pipeline_step_started is NOT included here because it already invalidates
// features.all() above, which also invalidates child queries (features.single)
if (
(event.type === 'auto_mode_feature_start' ||
event.type === 'auto_mode_phase' ||
event.type === 'auto_mode_phase_complete' ||
event.type === 'pipeline_step_started') &&
event.type === 'auto_mode_phase_complete') &&
'featureId' in event
) {
queryClient.invalidateQueries({