test: add testListenersOrder - #172
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #172 +/- ##
=========================================
Coverage 99.17% 99.17%
Complexity 111 111
=========================================
Files 7 7
Lines 364 364
=========================================
Hits 361 361
Misses 3 3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This tests the change in sabre-io#162 that makes sure not to sort listeners that are of equal priority, but to preserve the order in which they were created. Signed-off-by: Phillip Davis <phil@jankaritech.com>
provokateurin
approved these changes
Jul 14, 2026
This was referenced Jul 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This tests the change in #162 that makes sure not to sort listeners that are of equal priority, but to preserve the order in which they were created.
I ran these unit tests against the old code, and as expected, one of the test cases fails. The old code used to, somewhat accidentally, sort the events with the same priority into alphabetical order. We don't want or expect that to happen any more.