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

Allow a custom naming strategy #2

Open
yschimke opened this issue Jan 9, 2024 · 2 comments
Open

Allow a custom naming strategy #2

yschimke opened this issue Jan 9, 2024 · 2 comments

Comments

@yschimke
Copy link

yschimke commented Jan 9, 2024

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" }
@pemistahl
Copy link
Owner

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.

@pemistahl
Copy link
Owner

@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.

@pemistahl pemistahl reopened this Jan 12, 2024
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

No branches or pull requests

2 participants