Angular Rebooted: Components Everywhere
summary
A practical build of a webmail app using Angular 1.5 Component API demonstrates treating UI parts (folder list, message list, viewer) as self-contained components wired in a tree where data flows down and events bubble up. It advocates one-way inputs plus & output emitters instead of two-way binding, explains ngOnChanges with old/new values, shows ngMock tests that instantiate and render components, and argues this makes code more reusable, testable and easier to migrate to Angular 2.
AI-written summary · about
chapters (9)
- 0:00Angular introduction
- 5:52Complex app problems
- 8:50What is an Angular component
- 12:50Component input and binding
- 16:51Component output and data flow
- 20:07Component benefits
- 27:08Component splitting
- 31:27Component lifecycle and testing
- 32:51Migrating to Angular 2
related talks
27mThe good, the bad and the ugly - Component architecture at scale
47mTaking over the web platform with Angular 2
41mFrom .component() to @Component
36mBuilding framework agnostic UI with Web Components
29mThe Angular Renaissance
36mAngular, React, Vue and co: Harmoniously united by web components and micro apps?
21mAngular Elements Make The Best React Components
02h 47mAngular: The Renewal