Fix wrong event subscription in GroupStateTrigger and ItemStateTrigger #3533
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
GroupStateTrigger
subscibed toItemStateEvent
instead ofItemStateUpdatedEvent
(whileItemStateTrigger
usesItemStateUpdatedEvent
), this is confusiing and results in different behavior of both triggers.The
ItemStateTrigger
did not subscribe toGroupStateUpdatedEvent
which results in the trigger not firing for group state UPDATES. This is wrong because it fires for item UPDATES and for both, group and item CHANGES.