pablisco
07/23/2020, 9:54 AMarrow-android
where we can put all android related libs? and slowly move things like arrow-fx-android
and similar over there.
It will help with discoverability as well as remove Android build dependencies from other repositories (which can cause minor build time increases)aballano
07/23/2020, 9:55 AMarrow-fx-android
for thatpablisco
07/23/2020, 9:58 AMaballano
07/23/2020, 10:01 AMsimon.vergauwen
07/23/2020, 10:06 AMIO
.
I think it can go in the arrow-fx-coroutines-android
module as @aballano said since stream is already included in the single dependency that module would depend on.
I guess that would only include the vanilla bindings belonging to the sdk depedency.
Other things like leanback bindings, etc should go in follow the module system of Android itself I think.pablisco
07/23/2020, 11:12 AMarrow-android-binding-core
, arrow-android-binding-leanback
, etc. The fact that we are using fx and streams is an implementation detail IMHO, hence why I think it make sense to group all android libs together. Like, if we have extension properties to apply resources like Union<String, Int>
on Views in the future, that could be on a separate module, and it’ll be easier to find if they are all together.