The Tale Tell Code
summary
Claims that functions in templates force repeated dirty checking and slow apps, shows optional chaining can bloat minified output (one ? adds ~15 chars) and create unreachable, untestable code, and demonstrates refactoring a monolithic component into streams so subscriptions don’t leak. Uses Angular pipes and async pipe, RxJS BehaviorSubject, switchMap and takeUntil to push sort values, produce a VM stream, and remove seven open subscriptions caused by repeated sorts; the refactor shrinks component state and fixes the leaks.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:33Welcome
- 1:58Angular Change Detection
- 5:10Default Change Detection
- 7:12Optional Chaining
- 11:17Tightly Coupled Code
- 13:21Refactoring
- 16:10Subscriptions
related talks
34mBad Practices, how you should NOT do in Angular world
41mThe most infamous code smells in Angular Applications
29mHow to use Functional Programming with Angular and why it’s a good idea
35mBad Practices, what NOT to do in Angular
22mThe dark side of tuning Angular performance
34mNot Your Uncle’s Clean Code (TypeScript Edition)
27mWhy should You Care about Functional Reactive Programming
58mAngular and The Case for RxJS