You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AsyncOnSubscribe currently assumes I can trivially supply it with an Observable that emits up to n items. If you're abstracting over a callback based API there isn't an easy way to hook this in.
The current best way is to use a Subject, but this seems like a very heavyweight tool when the Observable is already going to be routed to a UnicastSubject in the AsyncOnSubscribe internals.
Are we meant to be creating backpressure-ignorant Observables using create(OnSubscribe) inside of the AsyncOnSubscribe callback?
Is there a way that we can provide a Subscriber<T> in the action in another overload to simplify the case where we want to abstract over something that's not already modeled as an Observable<T>?