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

Make sort more consistent accross uses and flags #869

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ariasuni
Copy link
Collaborator

@ariasuni ariasuni commented May 11, 2021

Fix #863
Fix #1030

In some cases, files were sorted twice, which in most cases is harmless.
But when two files are determined equal, their order is unchanged (because the sort is stable).
With --reverse, equal elements order, which wasn’t changed by the sort, were reversed twice (unchanged).

Also, command lines arguments are now sorted by their path.


I still need to check the xtests to see if anything’s wrong with my changes, and update the tests that needs it.

In some cases, files were sorted twice, which in most cases is harmless.
But when two files are determined equal, their order is unchanged (because the sort is stable).
With `--reverse`, equal elements order, which wasn’t changed by the sort, were reversed twice (unchanged).

Also, command lines arguments are now sorted by their path.
@micwoj92
Copy link

micwoj92 commented Jul 9, 2022

This branch has conflicts that must be resolved

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.

Option to sort by full path --reverse does not reverse in the case of a tie
2 participants