Convenience methods proposal

[sdelaysam]

@dmdevgo I'm considering your great framework to use in the next projects.
One thing that kinda bothers me is the need to write this code again and again

state.consumer.accept(...)
//or
observable.subscribe(state.consumer)

I understand this meant to unify the API but for end users it may be nice to have some convenience over it.

[dmdevgo]

@sdelaysam Thank you for the suggested improvements. The convenience issue is more complicated than it seems. For example, there is a need to write boilerplate code again or again like this .subscribe().untilDestroy() or correctly subscribe to the Action. Please see #46 and give us feedback on the proposed solution.

[sdelaysam]

@dmdevgo for me #46 decreased code readability. I like regular code .subscribe().untilXXX() (even if its repetitive) way more than Rx code in lamdas or initializers.
On the other hand, its fine for me to collapse several Rx operators into one if possible (like you did with bindTo)
Probably thats the way to go? (I'm not suggesting to name it "bindTo", just to illustrate the idea)

val count = state(initialValue = 0)
val buttonEnabled = state(false)

fun onCreate() {
    count.map { it > 0 }.bindTo(buttonEnabled)
}

[Jeevuz]

@sdelaysam Thanks for your proposals. We've discussed with @dmdevgo and I'm reviewed your changes and leaved comments with changes we ask you to make. Thanks in advance!

[sdelaysam]

@Jeevuz done!

[dmdevgo]

@sdelaysam resolve conflicts, please

[sdelaysam]

@dmdevgo done!

[Jeevuz]

@sdelaysam Thanks!