fix: prevents duplicated shortcut's callback immediate execution #98
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Current behavior: when registering a duplicated shortcut, the observable returned by the duplicate shortcut registration immediately emits
null
on subscribe, resulting in the shortcut's callback being executed immediately even though the shortcut wasn't triggered.Issue Number: 72
What is the new behavior?
The observable returned by the duplicated shortcut's registration is EMPTY, it never emits and completes immediately. This fixes the issue.
Does this PR introduce a breaking change?
If a consumer relies on the observable emitting
null
to detect duplicate shortcuts and trigger custom logic, then this change is breaking.It can be mitigated though: since rxjs
EMPTY
is a constant, one can check equality of the value returned byaddShortcut
andaddSequenceShortcut
to detect duplicated shortcuts:Other information
closes #72