How to mess up your Angular UI Components
summary
PrimeNG is a production UI library with ~200,000 downloads/month and real bug-history: implements ControlValueAccessor so form components support ngModel and reactive forms, uses ContentChild/ContentChildren with QueryList changes and must unsubscribe to avoid leaks, and replaces a custom template wrapper with ngTemplateOutlet and ng-container for correct DOM and events. Performance fixes include input setters + immutable objects instead of ngDoCheck, and wrapping heavy DOM listeners with NgZone.runOutsideAngular then re-entering the zone to update the UI.
AI-written summary · about
chapters (36)
- 0:00Intro
- 0:31About Cagatay
- 1:38About Primefaces
- 2:23About PramUI
- 3:00Timing
- 3:31Google decided to rewrite Angular
- 4:15Primate
- 4:37PrimaryAct
- 4:53Open Source
- 5:27Free Templates
- 5:56Polo
- 6:52Technical parts
- 12:56Content projection
- 15:20Dialogue projection
- 16:06Columns
- 17:25Tap
- 23:31DataView
- 25:51NG Container
- 29:00Change Action
- 31:26NGToCheck
- 32:41Setters
- 34:16Filter
- 36:21Change Detection
- 37:01Push Change
- 38:36Angular Control
- 40:46Zone API
- 41:36Event emitters
- 43:06Run outside Angular
- 44:31Run outside tables
- 45:46Game of Zones
- 47:31The problem
- 49:36The dragdrop service
- 50:31The tree service
- 52:16ngAfterView
- 52:41NFGlobalEvent
- 53:21NullPointerException
related talks
51mPrimeNG: Native UI Components for Angular
20mThoughtful Component Design
27mThe good, the bad and the ugly - Component architecture at scale
48mHandling Angular Forms Without Losing Your Sanity
40mAdvanced UI, Plugins and Components in AngularJS
34mHigh-Performance Applications with Angular
51mScalable User Interfaces with Angular 2
23mPerformance optimizations in Angular