-
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
Support Gradle 7.0's type-safe project accessors in auto-correct #52
Comments
This is currently partially working. ModuleCheck always knows the traditional, non-type-safe path. From here, it's easy to determine what the string value for the type-safe accessor would be.
Because we can figure out the type-safe version, we're able to look for type-safe versions inside the dependency blocks. So, removing or modifying an existing type-safe reference works. Adding type-safe accessors is not working. |
This was surprisingly working well for me when I tried. The main benefit of this tool is to find what can be removed so it is ok if |
https://docs.gradle.org/7.0-rc-1/userguide/declaring_dependencies.html#sec:type-safe-project-accessors
dependencies { // type-safe alternative to project(":commons:utils:numbers") implementation(projects.commons.utils.numbers) }
The text was updated successfully, but these errors were encountered: