Display dependency versions in descending instead of ascending order #189
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
|
I need some convincing (maybe an example) about why descending order would be more intuitive than ascending order here. |
In many cases (probably most cases) the most recent version will be used to resolve an inconsistency, so it makes sense to show the most relevant version first. |
|
I'll consider this in the coming days. The README would need to be updated to go along with this if accepted. |
|
@ddzz I'm ready to accept this, please rebase and update tests/docs, and show an example. |
bmish
changed the title
ddzz
force-pushed
the
reverse-version-order
branch
from
48fabf3
to
b8d33c2
Compare
|
@bmish PR has been updated. |
bmish
changed the title
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.
Before:
After:
