Compose All the Things
summary
Claim: using ember CPM macros, an auto-id attribute for selectors, and page objects yields concrete gains — Yahoo’s Ember ad platform runs across many apps with nearly 70 Ember developers, test coverage climbs from about 7% after adopting page objects, and a composable card component is built with content-projection registration that works albeit with some render-cost tradeoffs. The talk shows code patterns, the libraries used, and which pieces actually reduce boilerplate.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 2:09Agenda
- 2:48Ember at Yahoo
- 3:40What is composability
- 4:28Why is composability important
- 5:20Overview
- 5:31Who is this style for
- 6:07Declarative style
- 7:15Decouple classes
- 7:36Auto ID
- 7:57Style
- 8:23computed properties
- 9:54building blocks
- 10:36Ember CPM
- 15:38Example Card
- 16:11Yield Approach
- 16:51Markup Approach
- 17:29Content Projection
- 19:15Property
- 20:14Component
- 21:39Tests
- 24:07Page Objects
- 25:33Page Object Example
- 28:14Page Object Tips
- 29:34Conclusion
- 30:18Recap
- 31:21Child Components
related talks
01h 10mPanel: the future of Ember
35mPanel: Ember – Why and Where?
26mAmbitious UX for Ambitious Apps
26mBuilding Better Components
36mPanel: Ember at Scale
59mEmber.js, and why the framework helps you unlocking unprecedented productivity.
29mIdiomatic Ember, Sweet Spot of Performance and Productivity
24mNew to Ember: What ARE All These Things?
