-
Notifications
You must be signed in to change notification settings - Fork 13
fix: insert then cancel with workspace selected #626
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: insert then cancel with workspace selected #626
Conversation
The workspace selection case is broken
18e1d4f to
73bd75d
Compare
73bd75d to
886c4d4
Compare
886c4d4 to
3ee4f86
Compare
|
Fixed conflicts (just test imports). |
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.
Got it and I see #625 is already in. Sorry for the delay, I was out last week. I can merge once the conflicts are resolved.
This looks good for kb-exp, though I'm going to file a bug for us to rethink the mover APIs before this gets merged into Core as this feels a bit messy. Let us know if you have any suggestions!
|
Something else to ponder at the same time is scenarios like #635. Conflicts fixed, please consider this an unsolicited ad for git rerere. ➜ blockly-keyboard-experimentation git:(fix-ws-insert-cancel) ✗ git merge main
...
Resolved 'src/actions/move.ts' using previous resolution.
Resolved 'src/actions/mover.ts' using previous resolution.
... |
Fixes #623
The implementation conflated having no insertStartPosition with the block being new. But when the workspace is selected then there is no insert start position even if the block is new. Instead track whether we're inserting or just moving separately.
Demo: https://fix-ws-insert-cancel.blockly-keyboard-experimentation.pages.dev/