Description
When an onboarding step is moved in the graph, its connecting arrows move or reroute incorrectly.
Steps to Reproduce
- Open a member’s onboarding graph as a PM.
- Drag an existing step to a different position.
- Observe the incoming and outgoing arrows during and after the move.
- Repeat with a step that has multiple connections.
Expected Behavior
All edges remain attached to the correct handles and update smoothly while the node moves.
Actual Behavior
Edges shift into visually incorrect positions or follow unexpected routes.
Affected Component
Frontend
Environment
No response
Possible Cause
Not yet verified. Diagnose this on the branch or build used in the UX test — the tested graph editor was not found anywhere in the current main (see the companion issue on graph controls). For reference, the only related component in this repo, DiagramCanvas.tsx (a read-only competency diagram, built on React Flow), explicitly sets nodesDraggable={false} because its node positions are recomputed from a layout on every render; if the tested editor was built the same way, that same pattern — recalculating positions from a layout instead of tracking dragged coordinates — would be a plausible cause of edges rerouting incorrectly during a drag. Capture node coordinates, handle positions and edge state before and after dragging on the actual tested build to confirm.
Description
When an onboarding step is moved in the graph, its connecting arrows move or reroute incorrectly.
Steps to Reproduce
Expected Behavior
All edges remain attached to the correct handles and update smoothly while the node moves.
Actual Behavior
Edges shift into visually incorrect positions or follow unexpected routes.
Affected Component
Frontend
Environment
No response
Possible Cause
Not yet verified. Diagnose this on the branch or build used in the UX test — the tested graph editor was not found anywhere in the current
main(see the companion issue on graph controls). For reference, the only related component in this repo,DiagramCanvas.tsx(a read-only competency diagram, built on React Flow), explicitly setsnodesDraggable={false}because its node positions are recomputed from a layout on every render; if the tested editor was built the same way, that same pattern — recalculating positions from a layout instead of tracking dragged coordinates — would be a plausible cause of edges rerouting incorrectly during a drag. Capture node coordinates, handle positions and edge state before and after dragging on the actual tested build to confirm.