You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cons:
override conflict with Gradle API's(try inline?)
only supports implementation configuration
Improvements:
Change the name to avoid conflicts
Use configurations in name e.g. implementationDependencies = deps(...), testImplementationDependencies = deps(...)
API #️⃣2
// operator fun DependencyHandler.plus(...)
dependencies + deps(
androidx.navigation,
androidx.livedata
)
// OR
dependencies {
+ deps(...)
}
Pros:
looks similar to Forma Android
Cons:
only supports implementation configuration
Improvements:
Use configurations name in dependencies block:
dependencies {
implementation + deps(...)
api + deps(...)
}
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Deps plugin would be distributed standalone to accelerate adoption.
Deps API working just fine in Forma Android plugin but integration directly with Gradle configuration is not so simple.
We need to design an API
Make sure we coven all existing use-cases in Gradle configuration
API #️⃣1:
Pros:
looks similar to Forma Android
Cons:
override conflict with Gradle API's(try inline?)
only supports
implementation
configurationImprovements:
Change the name to avoid conflicts
Use configurations in name e.g.
implementationDependencies = deps(...)
,testImplementationDependencies = deps(...)
API #️⃣2
Pros:
looks similar to Forma Android
Cons:
only supports
implementation
configurationImprovements:
Use configurations name in dependencies block:
Beta Was this translation helpful? Give feedback.
All reactions