fix: improve drag overlay behavior in routine builder#452
Merged
aryandas2911 merged 2 commits intoMay 17, 2026
Conversation
aryandas2911
approved these changes
May 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📌 Description
This PR improves the drag-and-drop experience in the Routine Builder by fixing visual layering and interaction issues during task scheduling.
Previously, the dragged task card appeared behind the weekly schedule grid while dragging, which caused poor visual feedback. Additionally, after dropping a task into the schedule, the dragged card visually snapped back into the Task Library even though the scheduling action had already succeeded, making the interaction feel confusing and inconsistent.
This implementation uses
DragOverlayfrom@dnd-kit/coreto create a separate overlay-based drag layer, improving drag visibility and eliminating the confusing snap-back behavior.🔗 Related Issue
Closes #319
🛠 Changes Made
📸 Screenshots (if applicable)
before.vs.after.mp4
✅ Checklist