Pitfalls Of Using takeUntil and takeUntilDestroyed RxJS Operators

💥 Become a PRO with my in-depth Angular Forms Course💥
🔗 10% discount for the first 10 students - https://bit.ly/advanced-ng-forms-discounted

There are multiple patterns that allow us to handle unsubscription from RxJs streams when any component, directive, or anything else is destroyed. However, some of them have pitfalls that can make you think that you're safe but in reality, you can still have memory leaking. In this video, we will have a look at different ways to unsubscribe from RxJS streams and I will share with you which one in my opinion is the best one. If you like this video please share it with your colleagues and friends!

There is also a linter rule that can help you to catch those pitfalls:
https://github.com/cartant/rxjs-tslint-rules#rxjs-no-unsafe-takeuntil

🕒 Time Codes:
00:00:00 - Intro;
00:01:06 - Pitfalls using takeUntil operator;
00:05:38 - Other ways to handle subscription;
00:06:52 - The best way to handle unsubscriptions;
00:09:06 - Outro;

💡 Short Frontend Snacks (Tips) every week here:
Twitter - https://twitter.com/DecodedFrontend
Instagram - https://www.instagram.com/decodedfrontend
LinkedIn - https://www.linkedin.com/in/dmezhenskyi

#rxjs #angular #webdevelopment #decodedfrontend

Видео Pitfalls Of Using takeUntil and takeUntilDestroyed RxJS Operators канала Decoded Frontend