We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
build-logic
Currently, build-logic uses the gradle version catalog without type-safe accessors and the names of libraries and plugins are hard-coded.
For example, the AndroidFeatureConventionPlugin has the following code snippet:
AndroidFeatureConventionPlugin
dependencies { add("implementation", libs.findLibrary("androidx.hilt.navigation.compose").get()) add("implementation", libs.findLibrary("androidx.lifecycle.runtimeCompose").get()) add("implementation", libs.findLibrary("androidx.lifecycle.viewModelCompose").get()) }
With the gradle version catalog's type-safe accessors, the above code snippet can be replaced with:
dependencies { add("implementation", libs.androidx.hilt.navigation.compose) add("implementation", libs.androidx.lifecycle.runtimeCompose) add("implementation", libs.androidx.lifecycle.viewModelCompose) }
No response
The text was updated successfully, but these errors were encountered:
Per the comments in #318 , we want to wait until this is officially supported by Gradle without using a workaround that might be brittle.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Is there an existing issue for this?
Describe the problem
Currently,
build-logic
uses the gradle version catalog without type-safe accessors and the names of libraries and plugins are hard-coded.For example, the
AndroidFeatureConventionPlugin
has the following code snippet:Describe the solution
With the gradle version catalog's type-safe accessors, the above code snippet can be replaced with:
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: