Routing in Polaris
summary
Argues the next Ember router (Polaris) can be built from existing primitives — tracked decorator, cached and garbage-collection hooks like registerDestructor — so routes become composable resources with lifetimes that match their templates, eliminating stale route instances that cause leaks and weird model-hook behavior. Proposes a low-level tracked search param and a tracked URL primitive to unify query params as reactive I/O, enable parallel data and code loading, remove controllers, and keep routing predictable and testable.
AI-written summary · about
chapters (7)
- 0:00Introduction to Polaris
- 1:06Lifetimes and reactivity
- 7:14Understanding resources
- 13:14Router lifetime reform
- 18:53Data loading in routes
- 26:31Reforming query parameters
- 34:41Conclusion and call to action
