Q&A Panel
summary
AngularFire uses sockets and protobufs so interceptors don't work with AngularFire; use the Firebase emulators for reliable tests. The Angular router favors path-segment URL construction over named aliases. For route data, use guards with ngrx and push minimal data into the store rather than resolvers. Firebase features are modular (Analytics, Remote Config, Hosting) so pick what you need. Angular PWA + Firebase service worker integration is planned for a near release and ngrx-router exists as real GitHub code.
AI-written summary · about
chapters (6)
- 0:00Start
- 6:43The Angular Show - Official ng-conf Podcast
- 8:31ng-conf: The Musical 2021
- 12:31Author with Thinkster
- 13:11Q & A & James, Brandon, & Aaron Submit your questions
- 15:11Q&A & James, Brandon, & Aaron Submit your questions
related talks
23mProgressive Web Apps with Angular and Firebase
34mAngular is on Fire(base)!
49mLet Firebase help you to build better Web apps
39mAngular is On Fire(base)!
29mProgressive Web Apps with Angular and Firebase
45mReactive Angular 2
15mReducing package size and complexity with NgModule
31mProgressive Web Apps with Angular and Firebase
