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
Implicit option names should be kebabed #7400
Comments
@eriwen WDYT? And how would we deprecate the old properties? Or maybe save this up for Gradle 6.0? |
This does seem like a breaking change (if minor), so in my opinion it should be Gradle 6.0. Possibly I'd say "a contribution is welcome" but it would be kinda weird to have to save a PR for nearly a year to merge it. |
Yeah, that's what I was thinking. 👍 Well, I'm already excited for Gradle 6! 😆 |
We could have both options available and emit a deprecation warning for the non-kebab names. We should update the docs to say that specifying an |
This was waiting for Gradle 6.0 to do a small breaking change, now this train seems to be gone.. |
This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution. |
Would still be nice to have, not present in 6.7.1. |
Example:
The option name becomes
updateTemplates
but it should beupdate-templates
.The text was updated successfully, but these errors were encountered: