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:
Interesting feature request, thanks. I'm not familiar with Android development. What is the naming strategy in Android Studio? A combination of group and name? I'm not sure yet whether I will implement something like that, at least not as the default setting but maybe with a feature flag.
Please note that the scope of this plugin is only to deal with version catalog TOML files but not with dependencies defined in Gradle build files. For the latter, there exists the Gradle dependencies sorter plugin already where you might want to post your feature request, too.
@yschimke There is no need to close this issue yet. It is still reasonable to implement something like that for TOML files only in my plugin. As I said, I will think about it. Until I come to a decision, you can leave this issue open.
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: