cameleer/cameleer-server
1
0
Fork 0
Code Issues 42 Pull Requests Actions Packages Projects Releases Wiki Activity

Route diagram: error node highlighting #55

New Issue
Closed
opened 2026-03-14 21:37:15 +01:00 by claude · 0 comments
claude commented 2026-03-14 21:37:15 +01:00
Owner
Copy Link

Context

The diagram node rendering supports error styling (red glow, red border) via nodeStyles.ts, but the RouteDiagramSvg currently passes isError={false} for all nodes. Error status from the execution's processor tree is not propagated to the diagram overlay.

What's needed

  • In RouteDiagramSvg, determine error status per node from useExecutionOverlay data
  • Collect failed processor diagramNodeIds into an errorNodes: Set<string> in the overlay hook
  • Pass isError={errorNodes.has(nodeId)} to each DiagramNode
  • Error nodes should get red glow filter, red duration badge, and red arrowheads on connected edges

Acceptance criteria

  • Failed processors show red glow and red badges in the diagram
  • Edges leading to/from error nodes use the error arrowhead marker
## Context The diagram node rendering supports error styling (red glow, red border) via `nodeStyles.ts`, but the `RouteDiagramSvg` currently passes `isError={false}` for all nodes. Error status from the execution's processor tree is not propagated to the diagram overlay. ## What's needed - In `RouteDiagramSvg`, determine error status per node from `useExecutionOverlay` data - Collect failed processor `diagramNodeId`s into an `errorNodes: Set<string>` in the overlay hook - Pass `isError={errorNodes.has(nodeId)}` to each `DiagramNode` - Error nodes should get red glow filter, red duration badge, and red arrowheads on connected edges ## Acceptance criteria - Failed processors show red glow and red badges in the diagram - Edges leading to/from error nodes use the error arrowhead marker
claude added the featureroute-diagramui labels 2026-03-14 21:40:27 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
Accessibility (a11y) improvements
 bug
Something isn't working correctly
 cleanup
Code cleanup, dead code removal, refactoring
 epic
Epic: groups related issues
 feature
New functionality
 pmf
Product-market fit: critical for first market offer
 route-diagram
Route diagram page and execution overlay
 security
Authentication, authorization, RBAC
 ui
Frontend / React UI
 ux
UX/usability improvements
No Label feature route-diagram ui
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cameleer/cameleer-server#55
Delete Branch "%!s()"

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?