Is there anything in RxJava similar to this? <https://github.com/ReactiveX/RxSwift/blob/master/Docum...

# rx

[iex]

Is there anything in RxJava similar to this? https://github.com/ReactiveX/RxSwift/blob/master/Documentation/Traits.md#driver
More specifically Can't error out
I'd like that e.g. if I map a click button trigger to an api request an the api request fails, it executes again the next time the trigger is activated. Without having to create a new subscription each time.

[magnumrocha]

you can check the options here:
https://github.com/ReactiveX/RxJava/wiki/Error-Handling-Operators

[magnumrocha]

onErrorReturn onErrorReturnItem

[pt]

RxRelay might be what you want

[iex]

@magnumrocha onErrorReturn and onErrorReturnItem still cancel the stream

[iex]

@pt but relay doesn't have any error handling at all, right? My streams can fail. I just want to be able to continue listening after it.

[iex]

hmm I guess I could convert the inner Single to a Result or something... it's just not as convenient as Driver

[iex]

Driver is like LiveData, but it recovers from errors

[magnumrocha]

@iex to avoid your stream finish, you can combine it with flatMap (in case of Single) or `switchMap`:

disposable = reactiveLocationProvider.getUpdatedLocation(mLocationRequest)
        .buffer(50)
        .flatMap(locations -> mRestService.postLocations(locations).onErrorReturn { e -> emptyList() }
        .subscribeOn(Schedulers.newThread())
        .observeOn(AndroidSchedulers.mainThread())
        .subscribe()

[iex]

yeah, I'm aware that it's possible to nest the failable observable and recover from it. Hmm

[iex]

It's behaves similarly to driver actually, just a bit less nice to use

[iex]

I guess the nested observable can also be made to return empty() or similar

[iex]

if you don't have a meaningful fallback

[magnumrocha]

sure, this will depends of your business logic...

[iex]

ok, thanks @magnumrocha