Fixed bug in _.sortedIndex that put undefined at the start (FIX: #1834) #2042
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.
Changed _.sortedIndex function to hangle undefined values correctly (FIXES: #1834 )
Revised previous pull request: #2041
Previously
Changed it to:
The logic works because Undefined should be placed after the highest number possible + 1.
Based on @jdalton request in #2041 (comment) I added
NaNto always be placed after undefined.Based off of #1768 (comment)
The code aboves logic checks to see if the value is NaN, if it is go past
Infinityorundefined.So that how I built:
Since no numeric value can be greater than Infinity, it will place undefined values to the correct index.
And it will place all NaN past
Infinityorundefined.Also added edgeCaseTests, to verify it works: