You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When putting INI files into a repo, having the entries alphabetically sorted vs being unsorted / unordered, helps a little.
The idea is that things exist in some order in many places in codebases. So when you are unfamiliar with a project and see unordered information ... the question that comes to mind is "What on earth is this order???".
The second thing is purely a cosmetic issue where some projects I've worked on like the = to align. Again, common for some languages.
When putting INI files into a repo, having the entries alphabetically sorted vs being unsorted / unordered, helps a little.
The idea is that things exist in some order in many places in codebases. So when you are unfamiliar with a project and see unordered information ... the question that comes to mind is "What on earth is this order???".
The second thing is purely a cosmetic issue where some projects I've worked on like the
=
to align. Again, common for some languages.The PR #190 covers both of these features.
I'm not a JS expert, but the tests I've written provide the consistent output.
I also added tests that covered all combinations of the options (simply as permutations matter sometimes).
The text was updated successfully, but these errors were encountered: