I think that was the best explanation of those 3 operators I've ever heard. Thank you. Will be bookmarking this one. Cheers!
@kakaique2000
29 күн бұрын
Great video, we also have exaustMap that will ignore emissions while the current mapped inner observable haven’t been completed
@pezo1919
29 күн бұрын
Thanks!
@JoshuaMorony
29 күн бұрын
Yes, I think I use exhaustMap more than mergeMap actually
@elyoaprogrammer
23 күн бұрын
Excellent "A visual guide to" series!!
@lightyagami5963
29 күн бұрын
Great video! Just wanna extend 2 points: 1. the pull-based ixjs can also have all of the rxjs benifits without the back-pressure issue. 2. mergeMap with max parallel stream can handle the concurrent requests easily.
@pezo1919
29 күн бұрын
what are the downsides of ixjs?
@JoshuaMorony
29 күн бұрын
Interesting, I haven't actually come across IxJS before, will have to look more into it
@lightyagami5963
27 күн бұрын
@@pezo1919 1. less maintainer than rxjs, in hence has more potential bugs 2. not popular compared to rxjs, it may be rejected by your tech lead. 3. not easy to be reactive to the stream value, because you have to "pull" it explicitly, instead of "subscribe" it implicitly.
@pezo1919
27 күн бұрын
@@lightyagami5963 thanks! My assumptions were similar, nice to know!
@jordisarrato331
24 күн бұрын
I needed this video 2 years ago :D very usefull btw!
@michaelcasile1036
28 күн бұрын
I have to admit, these videos are sometimes a little complex for me, this one was excellent
@johncerpa3782
28 күн бұрын
Great explanation
@TheAUa
29 күн бұрын
Great visual explanation! Thank you
@DemystifyFrontend
29 күн бұрын
Good effort
@michaelsmall97
29 күн бұрын
What do you use for these visuals? I am interested in reactive visualization and have done some basic things myself, but if you used some tool I would love to know.
@JoshuaMorony
29 күн бұрын
I use Motion Canvas to create these, it allows using TSX to create animations. It doesn't give you stuff specifically for the reactive animations I have in the video, but it gives you the building blocks you need to build something like that.
@michaelsmall97
28 күн бұрын
This looks real cool, thank you
@Patryk-ok1ps
29 күн бұрын
Hey Joshua, thanks for the video. I have one question that I think I haven't been able to find a satisfying answer for. Let's say that we have the exact case scenario at the end of the video (7:39) BUT we also want to be able to modify only one entry in the request. If for example there's a comment field and the user changed it. We send a PATCH to the server but what about the frontend? Downloading the whole request again seems wasteful. One idea I had is to store the request in a ReplaySubject but that also seems a bit excessive. Do you know a clean way to do it? Thanks again =)
@JoshuaMorony
29 күн бұрын
There's different ways you can go about this, and likely it's going to depend on whatever tech/limitations you are working with, but ideally I like the mental model of just streaming data from the backend i.e. something like what Firestore provides - we just set up a stream of data from the backend for whatever we are interested in, and then it doesn't really matter what we or anyone else does to modify something in the backend, if anything changes we just get that data (and with something like Firestore we can just get the changes as well, we don't need to refetch everything)
@achrafbellaali5890
29 күн бұрын
For French speakers, these operators are also well explained in the course of openclassrooms
@larshanisch
28 күн бұрын
Code review comment: "request" should be renamed to "response", because it doesn't contain the request... 🍻
@JoshuaMorony
28 күн бұрын
fair call!
@larshanisch
28 күн бұрын
@@JoshuaMorony and I hope "share" is coming in a not too far future...
@JoshuaMorony
28 күн бұрын
@@larshanisch yeah that would make a sensible next video in this series actually, already mentioned it in one of the previous videos where we had both an error and data stream but haven't "zoomed in" on it like I did with switchMap in this video
@karamuto1565
29 күн бұрын
Good video I would also recommend using exhaustMap as an anti race condition operator. It's pretty much the opposite of switchMap as it only subscribes to the inner observable if the current one has finished and ignores in between emissions. This can be useful for example if you have something like a dialog that opens dependent on emissions from some stream.
Пікірлер: 27