Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(sorting): change keyIndex only when ranking changes #28

Merged
merged 1 commit into from
Aug 2, 2017
Merged

fix(sorting): change keyIndex only when ranking changes #28

merged 1 commit into from
Aug 2, 2017

Conversation

nfdjps
Copy link
Contributor

@nfdjps nfdjps commented Aug 2, 2017

Previously, keyIndex was getting updated before min and max ranking were checked, so it could change even if the ranking itself didn't, which meant that an item could get unnecessarily demoted.

Previously, keyIndex was getting updated before min and max ranking were checked, so it could change
even if the ranking itself didn't.
@codecov
Copy link

codecov bot commented Aug 2, 2017

Codecov Report

Merging #28 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@          Coverage Diff          @@
##           master    #28   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           1      1           
  Lines         103    103           
=====================================
  Hits          103    103
Impacted Files Coverage Δ
src/index.js 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fd2dd67...561677c. Read the comment docs.

Copy link
Owner

@kentcdodds kentcdodds left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@kentcdodds kentcdodds merged commit d621043 into kentcdodds:master Aug 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants