reactivex.github.io
reactivex.github.io copied to clipboard
ReactiveX
ReactiveX Website
It's still being discussed, but it seems like they're leaning toward adding this operator under some name or other to 1.x. See ReactiveX/RxJava#3443
The documentation at http://reactivex.io/documentation/operators/first.html is slightly wrong for the find operator, in rxjs at least. Documentation says that find emits `undefined` when no element matches. This is not correct, actually...
See ReactiveX/RxJava#4771 The behavior might be different e.g. between RxJava and Rx.NET
There are several new operators and operator variants that don't have marble diagrams. We also need to make a decision on how to diagram the new Completable, et al. observable-like...
From ReactiveX/RxJava#2293 "I think ReactiveX should be very careful to explain the difference between Observable.doOnError (side effect, will still blow up) and Subscriber.onError (last consumer, if handled here your error...
On http://reactivex.io/documentation/operators.html the "repeat" operator is categorized as a "Creating Observables" operator, which, in RxJava anyway, it isn't. in Rx.NET versions of repeat do initiate an observable sequence, so this...
...assuming this gets merged in: ReactiveX/RxJava#4179
There may be notes in the documentation about certain operators being "experimental" or "beta" when in 1.2 this is no longer the case, so update those. See ReactiveX/RxJava#4549