how do I convert `MutableLiveData` to `Observable`?

# android

[iex]

how do I convert MutableLiveData to Observable?

[Andrew]

What is the use case for this? Technically there is not a 100% accurate way to do this conversion since livedata sends its updates to lifecycleowners which observable is not. A lifecycle owner could update the observable based on the livedata changes as a sort of workaround to this but I can't think of a case where this would be needed.

[iex]

someone configured validation inputs in view model as live data, e.g. email, name, password...

[iex]

each has a live data, which is wired to the UI via data binding...

[iex]

now I want to process / validate these inputs, but this is kinda business logic so I want to do it with rx

[iex]

thus I need live data -> rx conversion

[iex]

I guess I can change the live data inputs if needed to something else, not sure what

[Andrew]

Here is a simple example on how validation is done with livedata. https://medium.com/swlh/basic-form-validation-in-android-with-live-data-and-data-binding-cb6b1d073717

[iex]

medium... can't read, article limit 🙂

[gsala]

I guess you have to use LiveDataReactiveStreams https://developer.android.com/reference/androidx/lifecycle/LiveDataReactiveStreams.html

[aoriani]

@iex Just use incognito

[iex]

@aoriani oh lol, I opened it in a different browser, thinking that it would react to the missing cookies but it didn't work? incognito works

[iex]

thanks

[iex]

ok, I checked it out, but I really would like to use rx and not live data to perform the validation. Have a bit more complex flow in mind and it becomes very unwieldy with live data

[Christophe Smet]

The conversion between the two is not optimal. I had problems with livedata being subscribed for ever. You could subscribe to a livedata en then emit it in a publisher perhaps ? But that all sounds pretty bad

[iex]

so should I just ditch live data for inputs?

[iex]

and leave it for view model -> ui only?