-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Fixed issue where can() returned false when the command was executable #5744
base: develop
Are you sure you want to change the base?
Changes from all commits
e010e7b
cd28cfc
cc6df2c
c3d12d4
adb6a81
6b08af8
944f77b
83e48ff
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The actual problem in this file is: if (!dispatch) {
return true
} There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Remove this section of code will resolve the current issue. However, it seems there is a deeper problem that needs to be addressed, which would involve a significant change. I will take your advice and work to close this PR as soon as possible. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is what the PR should be addressing. Everything else around this PR is incorrect with the intention behind can chains and how they should work |
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This test was correct. Please revert |
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.
I believe this is wrong.
If dispatch is true, commands will think that they can modify the
transaction
when they should not be able to.dispatch
should probably be namedshouldDispatch
where it beingfalse
means you should not, as a command, actually apply your change to the editor.