https://kotlinlang.org logo
#arrow-contributors
Title
# arrow-contributors
p

pablisco

07/23/2020, 9:54 AM
I’m investigating doing android bindings with Stream. Would there be any objection in creating a repository called
arrow-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)
a

aballano

07/23/2020, 9:55 AM
AFAIK we can use
arrow-fx-android
for that
p

pablisco

07/23/2020, 9:58 AM
Yeah, but may want to have different tools related to Android as separate modules
a

aballano

07/23/2020, 10:01 AM
I think it might depend on what you want to build, but I would encourage using that module since currently only holds 1 or 2 classes, so I don’t see the need for a separate one
☝️ 1
s

simon.vergauwen

07/23/2020, 10:06 AM
We're currently still missing a module for integration with KotlinX and Arrow Fx Coroutines. Same for Android and Arrow Fx Coroutines. Both modules are for
IO
. 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.
p

pablisco

07/23/2020, 11:12 AM
The other thing with bindings and android views is that there are multiple modules, so we wouldn't want to add every possible dependency on androidx... This is a place I'm planning to take inspiration from: https://github.com/ReactiveCircus/FlowBinding
I just realised I was saying the same thing @simon.vergauwen 😅 I was thinking something like
arrow-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.
3 Views