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
it would be good to have a way to set a standard naming strategy, by default maybe the names used by Android Studio when you follow the hint to add a new TOML dependency.
And rename in both the TOML and build files.
--- apacheHttpClient = { group = "org.apache.httpcomponents", name = "httpclient", version = "4.5.14" }
+++ httpcomponents-httpclient = { group = "org.apache.httpcomponents", name = "httpclient", version = "4.5.14" }
The text was updated successfully, but these errors were encountered:
Are you saying basically, not just sort the names as they currently exist, but change the names and also simultaneously update the version catalog to match those new names (also sorting the catalog, I imagine), as part of a new "power sort" feature?
It's not really part of DAGP either, but more like the role of an orchestrator (convention plugin in the above case) that runs DAGP, this sorter, and then other customizations to achieve a well-defined final goal.
Repeating from pemistahl/version-catalog-linter-gradle-plugin#2
it would be good to have a way to set a standard naming strategy, by default maybe the names used by Android Studio when you follow the hint to add a new TOML dependency.
And rename in both the TOML and build files.
The text was updated successfully, but these errors were encountered: