Hello Tobias, let's see if I can help with your questions.
why is there .subscribe?
In RxJs you need to subscribe to the observable to consume the values it produces.
how many responses do you expect?
An observable is a stream of values, it's like an array that grows over-time. For example, fromEvent(element, 'input').subscribe(x => console.log(x)) logs every time the input event is fired by element.
are they so many that they need to get mapped?
Yes, it's a stream of values.
where would you put a breakpoint in the declaritive code?
RxJs is both powerful and complex. It took me a long time to learn the basics, and I still make many mistakes with it. But I believe it's worth learning because it really gives a different perspective.
thanks, now you have described the api to me. I see, that in this style of code, everything is treated as a stream. However, an api request, a call via fetch, is fundamentally a single in and a single out. there is no stream of responses. The stream will always only have a single response or a single error. that is what async/await is about, and you get nice meaningfull stacktraces for debugging.
However, I agree most of the time it's not used that way. Still, treating everything as a stream has the advantage of making things composable and re-usable.
In any case, I'm not advocating for any approach. I should have made it more clear in the post. Also, you are right, I could have used async/await in the vanilla JavaScript code to make it look cleaner.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hello Tobias, let's see if I can help with your questions.
In RxJs you need to subscribe to the observable to consume the values it produces.
An observable is a stream of values, it's like an array that grows over-time. For example,
fromEvent(element, 'input').subscribe(x => console.log(x))logs every time theinputevent is fired byelement.Yes, it's a stream of values.
You can use tap as Felix mentioned.
RxJs is both powerful and complex. It took me a long time to learn the basics, and I still make many mistakes with it. But I believe it's worth learning because it really gives a different perspective.
thanks, now you have described the api to me. I see, that in this style of code, everything is treated as a stream. However, an api request, a call via fetch, is fundamentally a single in and a single out. there is no stream of responses. The stream will always only have a single response or a single error. that is what async/await is about, and you get nice meaningfull stacktraces for debugging.
It doesn't have to be, it can be a response stream:
However, I agree most of the time it's not used that way. Still, treating everything as a stream has the advantage of making things composable and re-usable.
In any case, I'm not advocating for any approach. I should have made it more clear in the post. Also, you are right, I could have used async/await in the vanilla JavaScript code to make it look cleaner.