-
Notifications
You must be signed in to change notification settings - Fork 611
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
[cmd] Revert Trigger implementation #4673
Conversation
a47db25
to
5df5d88
Compare
5df5d88
to
e6e60fe
Compare
/wpiformat |
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.
Taking back my approval temporarily: it occurs to me that perhaps this could be fixed at the Event
level instead? The problem still exists there.
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.
approved; stick a pin in this, though, we should use the delegation once the lower level is fixed. If we can't, the lower level stuff probably isn't really robust.
This takes Trigger out of the problem's effect; fixing BooleanEvent is somewhat lower priority (because no one uses it) and can be done separately. |
Is there a specific previous PR this is reverting? What are you reverting the implementation from and to? |
Trigger was refactored to use BooleanEvent when it was introduced in #4104, and this reverts to the original implementation. |
This might fix #4574 and similar.
There are no user-facing changes in this PR.