Strategy for visible errors with Rxjs

[jondot]

Hi,
I find errors very hard to troubleshoot mainly because rxjs will silently swallow and "fix" them (with the tryCatch wrapper, removing handlers etc. This renders some epics dormant without any visible error to indicate)
https://github.com/ReactiveX/rxjs/blob/01a09789a0a9484c368b7bd6ed37f94d25490a00/src/internal/util/tryCatch.ts

Other than activating break on exceptions, do anyone have a better workflow?

[jayphelps]

Hey 👋 oh no! In RxJS v6 errors should never be truly swallowed. Can you clarify what versions of redux-observable and rxjs you’re using and ideally provide way to reproduce?

[jondot]

Both latest as of today. In fact I’m upgrading from 5 to 6 and so I’m quite sure.
I’ll try to make an example

[Sawtaytoes]

I had to backtrack to RxJS v5.6-forward-compat because of issues with RxJS v6 and this was another one of those issues I ran into.

I was definitely having problems getting catchError to function like it used to. It was as if having a catchError didn't stop the entire observable from firing the error function on the subscriber. Is that the issue you were seeing too?