~/talk

Separate your concerns with router's resolver

Talkat Ng-Poland 2017 · on Tuesday, 2017-11-21· [angular, frontend-architecture]
slides:none on file

Adds concrete steps: implement Resolve<T> to return the HTTP Observable so the Router waits for data resolver waits for Observables and Promises, remove HTTP calls from component constructors and read values from ActivatedRoute.snapshot.data, compose multiple resolvers for shared endpoints, use Router.events to show a single global loader instead of per-resolver notifications use Router.events to show a single loader, and register a Router errorHandler to centralize resolver errors register a Router errorHandler for global error UI.

AI-written summary · about

  1. 0:00Introduction
  2. 1:40Agenda
  3. 2:04Why resolver
  4. 5:25The app
  5. 6:54Under the hood
  6. 9:52Create basic resolver
  7. 12:51Create other resolver
  8. 13:25Two resolvers
  9. 14:43Service
  10. 15:36Router Events
  11. 16:21Error Handling
  12. 17:16Error Handler
  13. 18:19Summary
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.