What's the hardest thing TIMING! about async?
summary
Async derived data causes subtle bugs so the work shows five concrete iterations from a naive constructor fetch to a reusable resource that actually cancels in-flight requests via abort controller, registers teardown with Ember destroyable APIs, caches and updates instead of recreating handlers, and finally wires into community implementations like ember-resources and ember-concurrency. The examples are on GitHub, network requests abort correctly, reactive updates work, and the resource approach proves shorter, more composable, and reliable.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:57A strange land
- 2:20I thought it was easy
- 4:15First attempt
- 6:28Second attempt
- 8:45Third attempt
- 11:18Fourth attempt
- 16:20Resources
- 18:06Promise Handler
- 19:10Template Helper
- 19:52Ember Resources
- 21:10Ember Concurrency
