broo the extended class approach is genius

The last part at 09:12 is very nice indeed. I really like this kind of work. A great solution for many applications. Once again, great content my friend. 👍

You are awesome sir, keep making videos like this !!! You are teaching a lot of newbies and experienced programmers!!

superb explanation of all possible ways of avoiding memory leaks for RxJS subscriptions. Thank you so much ! 🙂

Excellent short and consolidated walkthrough. Thanks for posting.

This channel is underrated.

High quality information as always. Many thanks Oleksandr!

You provide very valuable content, thank you Olexander PS Olexander, consider creating new angular course but even more advanced than medium one - by saying more advanced i mean using bigger spectrum of RxJs operators, change detection strategy, NG rx, using facade pattern, and such tricks like this one with extending abstract class, strict mode, use of firebase? This is just my idea, but knowing your skills as a teacher and experienced developer it would be Very valuable and helpful for developers on any 'level', best regards and stay healthy!

Дякую! Дуже круте відео, все чітко і зрозуміло!) Thanks a lot!)

Amazing post. Maybe you'll make more with RxJS and also with complex Directives. Thank you!

Excellent video, I think I'm gonna stick to async pipe and avoid suscriptions, Oninit and Ondestroy altogether in my code...

Best and straightforward...but i just see in my navbar one of your videos.. that async pipe is broken in Angular

Brilliant! Thank you.

This is pretty awesome! Love that's it's so easy to implement but so valuable. Thanks!

Many Many Thanks to you sir, You make my day

amazing explanation. super helpful!

Thank you ! Very useful information !

Legend! Thanks for the awesome content especially the custom takeUntil(), pretty useful

Thank for your awesome content

Nice video 👍 I would just like to mention that since version 16, Angular has introduced the "takeUntilDestroyed()" operator, which solves this problem. One question, why did you decorate the parent class "Unsub" with "@Injectable()"? In your example, it is not used as a service provided via dependency injection. Thanks!

Awesome content on unsubscribe

Very nice video man, congrats! Could you make a video talking about the new operator released in Angular 16, the "takeUntilDestroyed()"

Thank you for the good content 🤩

Hi, i find this approach very interesting also. DO you might wanna do a short video about that option too. takeUntilDestroyed with destroyRef which close "Automatically" the sub.

Premium content, useful information. Thank you

Sorry for the dumb question, but what if I have: data$ = interval(1000); const x$ = this.data$.pipe(take(1)); x$.subscribe((data) => console.log('data', data)); Which of the observables does the take(1) operator specifically complete?

You re the best! Tnxx!

Is it correct that we should use ReplaySubject, NOT Subject for unsubscription? After component destroyed it is possible that Subject is destroyed too, but subscription NOT. And subscription survive after destroy. But ReplaySubject can "shot" one more time after component destroy and subscription will be completed.

Hello! I love your video so much. Where is the best place to support you? On your platform or udemy (as far as I know udemy takes some commission)?

amazing stuff, we need to call super right if we use this class as a common for all components ?

What should we do if we need ngOnDestory in the child component or how we can override it?

Thanks!

Крутотень)

you'll need a super() call in the component's constructor using / extending this class, otherwise TS will complain?

Should i unsubscribe route change as well

how would you call abstract unsub class while your component already extends other class? in typescript you cant extend two class. do you have any thoughts about that?

I still remember several projects where the people forgot to close subscriptions...

Hi, can you tell us which IDE you are using? :)

Wait what? I was sure the component is destroy when not in the view anymore and by consequence all subscribe are unsubscribed…

why don't we just use a promise for queries? this sounds like a potential problem in your app to troubleshoot.

Monster! 😂

I don’t feel like the video is useful at all, this can be found in angular doc and this is far from real life situation (interval really ? ..)

Last one approach is nice but it does not allow to use "ngOnDestroy" in the "Postscomponent" as it is already declared in "Unsub".