Channels
#rx
- p
peasee
07/17/2017, 9:55 AMdat rx learning curve is steep 😕 thanks again - b
bachhuberdesign
07/17/2017, 5:07 PMAndroid question: Is using LiveData together with RxJava a bad idea? Here’s what I was thinking: View will observe LiveData from the ViewModel. ViewModel will subscribe to Single<Response> from the repository/network service. When we get a response in onSuccess(), post it to the LiveData for View to consume - b
bachhuberdesign
07/17/2017, 5:08 PMThat way we get all of the benefit of lifecycle management from the LiveData but still have the flexibility of RxJava for our call adapter (Single<Response> & Observable<Response> depending) - b
bachhuberdesign
07/17/2017, 5:09 PMThis is with Retrofit by the way - j
jw
07/17/2017, 5:11 PMwhy bother with LiveData then? - j
jw
07/17/2017, 5:12 PMif you're already using Rx then you can just propagate the data up into the UI with an Observable that's composed of other data sources - z
zak.taccardi
07/17/2017, 5:12 PM
has little value if you are already using RxLiveData<T> - b
bachhuberdesign
07/17/2017, 5:12 PMWould you suggest that it handled manually? Or should I use a library like RxLifecycle? - z
zak.taccardi
07/17/2017, 5:13 PM
is still useful though for scoping aViewModel
to the full lifecycle of the current UI (and surviving config changes)Relay<T> - z
zak.taccardi
07/17/2017, 6:05 PM@bachhuberdesign It’s simple enough to forward `onStart()`/`onStop()` to your
. begin observing inViewModelonStart() - z
zak.taccardi
07/17/2017, 6:06 PMand your
which houses yourRelay<T>
pojo will survive config changesViewState - b
bachhuberdesign
07/17/2017, 6:36 PM@zak.taccardi Makes sense. I am going to try writing something similar to that. Thanks for the response - b
bachhuberdesign
07/17/2017, 6:40 PMWould you suggest using
and then just replaying all events after a configuration change?ReplayRelay - b
bachhuberdesign
07/17/2017, 6:40 PMNever used RxRelay before so I’m trying to wrap my head around it - z
zak.taccardi
07/17/2017, 7:31 PMuseBehaviorRelay<T> - z
zak.taccardi
07/17/2017, 7:32 PM
replays ALL events ever sent to it to new subscribersReplayRelay<T> - z
zak.taccardi
07/17/2017, 7:32 PM
will emit the most recent eventBehaviorRelay<T> - t
tulio
07/17/2017, 9:20 PMDo you guys return some kind of obseravable on database insertions? - b
bachhuberdesign
07/17/2017, 9:22 PMWhat are you using? SQLBrite? Room? - b
bachhuberdesign
07/17/2017, 9:23 PMReally depends on what you want to do. I only return int/long ID after inserts usually (if I actually need them) - t
tulio
07/17/2017, 9:41 PM@bachhuberdesign I'm using Room - t
tulio
07/17/2017, 9:42 PMRight now I'm doing this:Single.fromCallable { database.itemDao().insertAll(items) } - z
zak.taccardi
07/17/2017, 9:42 PMwhy? - z
zak.taccardi
07/17/2017, 9:42 PMoh for inserts - z
zak.taccardi
07/17/2017, 9:42 PMyes, single is appropriate - t
tulio
07/17/2017, 9:43 PMSo my inserts return aSingle<List<Long>> - z
zak.taccardi
07/17/2017, 9:43 PMCompletable doesn’t handle passing info in
callsonNext() - z
zak.taccardi
07/17/2017, 9:43 PMwhich you would need to handle exceptions within the stream - z
zak.taccardi
07/17/2017, 9:44 PMmemory full exception or somethign - t
tulio
07/17/2017, 9:44 PMMakes senses