-
Notifications
You must be signed in to change notification settings - Fork 4.6k
List View: Remove unused selector from the 'useBlockSelection' hook #48984
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
Conversation
|
Size Change: -4 B (0%) Total Size: 1.34 MB
ℹ️ View Unchanged
|
|
@alexstine, this shouldn't affect any work done that PR. |
alexstine
left a comment
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.
With the above confirmed, LGTM. 👍
andrewserong
left a comment
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.
Thanks for spotting this one @Mamaduka — from memory, I was originally playing around with using getBlockSelectionEnd and eventually realised that the end of the selection would always be using clientId or destinationClientId instead, so this looks like a stray leftover from that exploration.
Thanks for the caution @alexstine! From testing this PR out with each of the keyboard and mouse combinations for multi selection within the list view, this change appears safe to me, and doesn't seem to impact the other in progress work.
LGTM!
|
Thanks for the reviews and additional context 🙇 |
What?
PR removes the unused
getBlockSelectionEndselector from the 'useBlockSelection' hook.Why?
I don't believe this selector was ever used (introduced in #38314), so it doesn't affect the
updateBlockSelectioncallback.Testing Instructions
CI tests are passing.