How to debug rxjs5?

Question

In RxJS - Goals I read that their goal is to better debug:

goal

Provide more debugged call stacks than previous versions of RxJS

I was just starting to use redux-observable , which made it easier for me to understand by comparing it with redux-saga , since I’m already used to the reactive style with lodash and ramda (ok, fp style maybe;). I was surprised that it was not yet possible to debug it. It's true? If so, then I should switch to redux-saga , perhaps, or stick with redux-thunk .

Edit based on J Phelps answer

By debugging, I meant: "How to set a breakpoint, for example, observable.map(...) in the browser?" With lodash I can set a breakpoint in the browser, and it stops right on _.map(...) . How to do this with redux-observable (or rxjs )? I don't want to depend on drawing marble charts and console.log() .

Answer 1

Of course, you can debug RxJS code. I think that it is probably safe to say that hardly anyone will use it if it is not - Angular2 is also heavily built on it.

The most common ways users use it is the same as debugging other JavaScript, breakpoints (like a debugger) and console.log ()

There are more advanced methods that some users use, such as graph dependency graphs or marble charts. Andre Stalz wrote about this , so this can be a useful resource.

Ultimately, any asynchronous programming will be harder to debug. This is not unique to reduction-observables / RxJS; a quick search will reveal many debugging problems for the reduction saga.

It turns out that redux-thunk is the best solution for the vast majority of applications built because most of them do not have complex side effects that justify something like a redux-observable or reduction saga. Although, if you already own RxJS, there is nothing wrong with using a shortened view.

redux-saga, since the project existed longer than the contracting one, so it is certainly one of the main selling points. You will find more documentation, examples, and probably get a better community to get support.

The counter is that the operators and APIs that you learn in the sound release are not as portable as the RxJS training, which is used universally. redux-observable is super super super simple inside, it really just gives you a natural way to use RxJS. Therefore, if you know RxJS (or want), this is a very natural fit.

My advice at the moment for most people is that if you need to ask which one you should use, you probably should choose the very one itself.

(disclaimer: I am one of those who support reduction and RxJS v5)

Answer 2

 import Rx, { Observable } from 'rxjs' const arrStream$ = Observable.of(1,2,3) .do(x=>console.log('Before',x)) // 1, 2, 3 .map(x=>x*2) .do(x=>console.log('After',x)) // 2, 4, 6 .subscribe(value=>doThingsWith(value)) // real console output // Before 1 // After 2 // doThingsWith(2) // Before 2 // After 4 // doThingsWith(4) // Before 3 // After 6 // doThingsWith(6) 

.do (debugValue => console.log (debugValue))