That's really not a managable way of handling rx. ...

# rx

[Paul Woitaschek]

That's really not a managable way of handling rx. That puts ton of state all over the place. Just call executeRequest a couple of times and you're into the fun 🙂

[ubu]

@Paul Woitaschek, thanks. what would be the manageable way then?

[Paul Woitaschek]

Transform the stream without the side effect

[Paul Woitaschek]

Have one class which represents the state

[Paul Woitaschek]

For exmaple you have a selead class RequestState with an RequestState.Error(throwable), RequestState.Success(data), ...

[Paul Woitaschek]

Then use onErrorReturnItem(Error), startWith(Loading),...

[ubu]

@Paul Woitaschek, thanks. would you separate streams using, say, BehaviourRelay? Like in the example we’ve just discussed.

[Paul Woitaschek]

No, that's the point. That way you have everything scoped in one stream and no issues with mutliple subscribers etc.

[ursus]

How do you flatmap 2 observables returning those state objects? you have to add filters for Started events etc, makes code super messy imho

[Paul Woitaschek]

You don't, you only use it on consumer site

[ubu]

@Paul Woitaschek, have you got some cool examples at hand?

[ursus]

yea, but how do you know..it means those methods dont compose, you then have to extract methods which are the same but without the methods, public api is then murky, idk..