fix(sidebar): prevent missed clicks during rapid workflow switching (keep row drag)

[waleedlatif1]

Summary

Prevent missed clicks when rapidly switching workflows by gating navigation on active drag state rather than a transient drag-start flag. Keeps full-row drag-and-drop intact.

Fixes: N/A (surgical UX bugfix)

Type of Change

• Bug fix

Testing

• Rapidly clicked multiple workflows (not intending to drag): each click navigates immediately.
• Intentionally dragged rows between folders and to root: DnD still works; payload (workflow-ids) unchanged.
• Shift+click multi-select, rename input, and hover edit button behaviors unchanged.
• Marketplace/editing states still disable drag as before.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• No new warnings introduced

Screenshots/Videos

N/A

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
sim	Building	Preview	Comment	Sep 7, 2025 2:51am

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Skipped			Sep 7, 2025 2:51am

[greptile-apps]

Greptile Summary

This PR fixes a UX bug in the sidebar's workflow navigation where rapid clicks on workflow items could be missed during workflow switching. The issue was caused by a timing mismatch between the drag state management and click handling logic.

The change modifies the workflow-item.tsx component within the sidebar's folder tree structure. Previously, the click handler used dragStartedRef.current to determine whether to prevent navigation clicks, but this ref was set synchronously during drag start and only reset asynchronously via requestAnimationFrame during drag end. This created a problematic window where legitimate clicks could be blocked even when no actual drag operation was occurring.

The fix replaces the ref-based check with the isDragging state variable, which is managed synchronously with the actual drag lifecycle. When a drag starts, setIsDragging(true) is called immediately, and when it ends, setIsDragging(false) is called before the asynchronous ref reset. This ensures that the click prevention logic accurately reflects the current drag state, allowing immediate navigation when users aren't actively dragging.

The change integrates well with the existing sidebar architecture, which uses the folder tree component to organize and display workflows. The drag-and-drop functionality remains fully intact, including multi-select operations, rename inputs, and marketplace/editing state handling. The dragStartedRef is preserved for any other potential uses but no longer interferes with the primary click navigation.

Confidence score: 5/5

• This PR is safe to merge with minimal risk
• Score reflects a surgical fix to a specific timing issue with clear before/after behavior and comprehensive testing coverage
• No files require special attention

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}