Ember Component Patterns
Todd Jordan
A Little About Me
Triangle Ember Meetup Organizer
Ember Learn Team
A Little About Ember
Commitment to Semver, "Stability without Stagnation"
Convention over Configuration
Pre-Built Local Environment and Build Pipeline
(node, tests, linting, es6)
Community Owned and Maintained
A Little About This Talk
Components are Everywhere
Lessons Forged in Fire
Not Dogma, but understand your tradeoffs
Basic Component Mechanics of Ember
Inspire some ideas, thoughts
Basics of an Ember Component
Functional Components and DDAU
Ember's sweetspot
Tradeoff
Predictable vs. In Control
Data Morphing "Tagless" Components
Adding Decoration
Tradeoff
Simple vs Declarative
Alternative: Handlebars Helpers
Block Components
Ultimate Flexibility
Tradeoff
Customization vs Easy Defaults
Coodinating Components
Easy Reuse
Tradeoff
Ease of Use vs Power Over State
Service Event Bus
Communicating Across Complexity
Tradeoff
Predictable Data Flow vs. Data Flow Complexity
Anti-Patterns
Giants
Antidote
Sub-Components - Create building blocks
Single Responsibility
JQuery as a hammer
Antidote
Use it within the proper scope as a last resort
Return Promises from actions
Coupling to App Implementation
Antidote
Adhere to DDAU
Treat Services like data, push them up the tree
Service Mayham
Antidote
Limit service injection to top level or coordinating components
Avoid Circular Service Dependencies
Adhere to good programming principles
Use Ember Data for persistence when you can
Thanks!!!
Twitter: @tddjordan
Github: toddjordan
Slack(Ember, Triangle): todd.jordan