fix: sorting symbols when the field is null #496
Merged
Conversation
This file contains 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
|
Merged! |
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.
Description
This PR is going to fix the #491 issue.
We were assigning big numbers for nullable fields when sorting our monitoring symbols such as
Sell - Profitwhich makes the sorting in Mongo DB unstable.Based on that, we rely on
$symbolfield instead of big numbers when the fields are null to make the sorting functionality work as expected.Related Issue
#491
Motivation and Context
How Has This Been Tested?
Tests have been written to verify that.
Screenshots (if appropriate):
Refer to #491