Rxjs Streams in Angular - Normalizing Data (Map and Pipe Operator)

In this video you will learn what are RxJS streams in Angular. We will check on the real example how convenient it is to use RxJS map and pipe methods for normalizing data inside our service from observables which we are getting from API.

MOST POPULAR COURSES

SERVICES THAT I'M USING

CONNECT WITH ME!

REFERENCES

TIMESTAMPS
0:00 Introduction
1:26 What are streams in RxJs
3:40 Normalizing data with RxJs in Angular
6:04 RxJS pipe and map methods
11:39 Call to action

This video is NOT sponsored. Some product links are affiliate links which means if you buy something I'll receive a small commission.

[manojkarthik]

He may be talking like a robot but the content is extraordinary.

[TauwinKul]

Your intro and outro are world class. Not to mention the content of your short videos.

[charleso]

Very well explained. Its difficult sometimes finding a clean explanation of these functions but this one helped me actually understand it properly. Thank you!

[mybootscamewithoutstraps]

I can see that you've made improvements over the years with your videos to work on how you use inflection in your voice. It still feels really robotic when listening to the content, but you definitely have concise lessons that get things across the way they need to be.

[ayushd]

Thank you so much! I have seen around 10 videos on this topic and this is the best video that has cleared my doubt! Subscribed!

[leandrodossantos]

Bro, I found this a little later but it is a great explanation, thanks man!

[omar-elgammal]

such a great Explanation ! keep up the great work

[ilkerberkeelcioglu]

Very well and detailed explained. Thank you, it was very helpful!

[MrCyurasys]

Your video is very good.
I have only one mention:
In method getUsers you could have used return users.map(user => user.age += ' years old')
I dont think it is needed to return a new object but just return the same one and modify only the properties you need

[Georgii]

Hello! Thanks for the excellent tutorial. One question. In the UserService, if I want to implement a method that returns Observable of only one user, the youngest one, what would be the code ? The important thing is that I want the service to return the observable of this user...So sorting by age would be done in the service, on the list of users.

[dipabhow]

Very good video for map operator... thanks for it man...

[abdulaziz]

excellent sir, very helpful real-time example

[adhivenkatesh]

Hi Olex, its great video, is there any videos for angular chatbot with room, videos need for tips in angular

[luca-rwss]

Very Very good explanation! Thank you.

[kshitijbhatt]

Is the online course still maintained? The website didn't look really responsive hence I am skeptical. But this is the best video i have seen on rxjs streams for angular. Really interested in advance angular course if it's still maintained.

[BGivo]

One thing I don't quite understand. When you "subscribe" to a stream, and the value in the stream changes, would the component that was subscribed to it automatically render on its own? (or is this something you need a BehaviourSubject for?)

[HoNow]

Very cool angular videos!! But please you should think about using a more friendly IDE like VScode :)

[amannegi]

awesome video, but try smiling sometimes.. :)

[auchucknorris]

at 10 minutes is exactly why i dislike typescript, front end code your constantly manipulating data, so much extra work, for a benefit that doesn't matter on front end code, ur not going to ruin a database so its only purpose is to throw errors

[dennsr]

I don't see why http requests are observables. Observables can only have ONE observer, and HTTP requests will complete or error after they are executed. Yes, I can combine multiple observables and mutate their data, but I can do that with promises as well ... native. Plus I can simply await one or multiple promises that can be fired sequentially or all at the sime time. And I do not have to store subscriptions to unsubscribe if my component destroys itself.

Subjects can have multiple observers and they can emit different values over time, okay I can see the use of that, but I don't understand why http requests are observables. The ONLY usecase, where observables are superior in http requests is when I can use switchmap to cancel them. But for that I need an input stream as well ... 🙄