-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
[plugins]
section in libs.versions.toml
is moved to the top by refreshVersions
#690
Comments
libs.versions.toml
is moved to the top by refreshVersions
[plugins]
section in libs.versions.toml
is moved to the top by refreshVersions
TBH, I'd say it would be best if there was an option whether you want the sections to be in "standard" order, or left as-is. Related discussion: littlerobots/version-catalog-update-plugin#113 |
Right, my biggest problem is that it doesn't keep my ordering. I believe refreshVersions should either force the standard ordering, or respect the user's ordering. If the latter, it removes the need to add any configuration and everyone is just happy :) |
🐛 Describe the bug
Not a real bug per se, but an annoyance. The order of the sections in the generated
libs.versions.toml
is unusual (plugins
comes first, beforeversions
).It would be better if
plugins
were at the bottom for the following reasons:versions
section is the thing that we update the most, and manually, so it's nice if it's easier to access - at the topplugins
usually reference version numbers from theversion
section, and it's more natural for version references to appear after version declarationsversions
,libraries
,bundles
,plugins
The
plugins
section is moved to the top.✅ Expected behavior
The
plugins
section stays wherever it is, or is moved to the bottom.💣 Steps to reproduce
Create a
libs.versions.toml
with aplugins
section. For instance:Then run
refreshVersions
and notice that theplugins
section moved.The text was updated successfully, but these errors were encountered: