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
When util.tryWithObserver is used, the scope of error capturing is too wide, so any error from handlers are captured either.
The following example is from the operator all:
localfunctiononNext(...)
util.tryWithObserver(observer, function(...)
ifnotpredicate(...) thenobserver:onNext(false)
observer:onCompleted()
endend, ...)
end
In the above case, the util.tryWithObserver function is covering not only the invoke of the predicate function but also covering the invoke of onNext and onComplete of the Observer.
The observable emits errors from onNext of the observer to onError of the Observer even the error is not from the Observable.
I think util.tryWithObserver function should cover only the invoke of function belong to the Observerable itself.
The text was updated successfully, but these errors were encountered:
When
util.tryWithObserver
is used, the scope of error capturing is too wide, so any error from handlers are captured either.The following example is from the operator
all
:In the above case, the
util.tryWithObserver
function is covering not only the invoke of thepredicate
function but also covering the invoke ofonNext
andonComplete
of theObserver
.The observable emits errors from
onNext
of the observer toonError
of theObserver
even the error is not from theObservable
.I think
util.tryWithObserver
function should cover only the invoke of function belong to theObserverable
itself.The text was updated successfully, but these errors were encountered: