Open AfigAliyev opened 2 years ago
Currently, build-logic uses the gradle version catalog without type-safe accessors and the names of libraries and plugins are hard-coded.
build-logic
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
Per the comments in #318 , we want to wait until this is officially supported by Gradle without using a workaround that might be brittle.
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