-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(comments): added workspace comments and comment drag strategy isDeadOrDying() checks (for multiselect plugin) #8532
Conversation
…ded blocklyDraggable class to ws comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change seems pretty reasonable even absent any context other than that it makes comments consistent with blocks, so I'll go ahead and approve this.
There is one other thing, though: screenshots are not very searchable. Can you supplement them with markdown-formatted text and/or (since they seem to be screenshotted from another GitHub conversation) a link to wherever page they originally came from (if public)?
I'm going to go ahead and merge this, but @changminbark please update the description to make it easer to search. |
The basics
The details
Resolves
Fixes #8531
Proposed Changes
Added the isDeadOrDying() checks for the workspace comment's isDeletable and comment drag strategy's isMovable methods (such as the ones that are already implemented for blocks.
Reason for Changes
Fixes a bug in the multiselect plugin:
After multiselecting comments, copy/pasting them, and then undoing that action does not get rid of the comments from the multiselection. This is usually not a problem as it also happens to blocks. However, the blocks and comments have different isMovable (drag strategy) and isDeletable methods, which lead to a breaking behavior in the multiselect plugin. I have already tested a fix for this by implementing the missing isDeadOrDying() check for the isMovable and isDeletable methods for comments.
Test Coverage
Documentation
Additional Information