-
Notifications
You must be signed in to change notification settings - Fork 7
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
Format dependencies in order to have consitent look and feel #6
Comments
Thanks for an idea and reporting it. |
I would go for the format which can be used with closures and I would use Groovy string in order to support variable replacement. -> implementation("org.apache.commons:commons-lang3:$commonLangVersion") Gradle (understand Groovy) is confusing because of the numerous syntax that are available. It would be good for développeuse to have all the time the same format. I think that this format also helps clarifying that behind it corresponds to a standard method call. Other options if you don't like forcing people:
|
Why not making it configurable in the settings? |
Or better, why not making it project level thing? because every project might have its own better convention. |
The settings might be like this:
|
I generally prefer
The parenthesis adds too much visual distraction and I would only want that distraction if the above version is not able to do it (e.g. if exclusions are needed) as it will visually indicate deviating from the defaults. |
The plugin should in addition of reordering dependencies also format them in order to have consistent look and feel.
Example:
->
The text was updated successfully, but these errors were encountered: