-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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: ICommadSource Implemetation #15496
fix: ICommadSource Implemetation #15496
Conversation
You can test this PR using the following package version. |
Note that whatever is decided here also must be done to |
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.
These changes make sense.
If we want to define this as an expected behavior, it should also be unit tested (i.e., changing Command inside of CanExecute handler or something obscure like that).
Also, SplitButton, yes.
@cla-avalonia recheck |
|
@cla-avalonia agree |
b3b7533
to
99af069
Compare
You can test this PR using the following package version. |
5e8b374
to
fe7c841
Compare
You can test this PR using the following package version. |
* test: CommandParameter does not change between CanExecute and Execute * feat: CommandParameter does not change between CanExecute and Execute * test: update
What does the pull request do?
Ensure CanExecute and Execute consistence.
What is the current behavior?
The current implementation of ICommandSource does not guarantee that CanExecute and Execute occur on the same command.
What is the updated/expected behavior with this PR?
How was the solution implemented (if it's not obvious)?
Checklist
Breaking changes
Obsoletions / Deprecations
Fixed issues