You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17-4
Original file line number
Diff line number
Diff line change
@@ -14,14 +14,26 @@ AngularFire smooths over the rough edges an Angular developer might encounter wh
14
14
-**Google Analytics** - Zero-effort Angular Router awareness in Google Analytics
15
15
-**Router Guards** - Guard your Angular routes with built-in Firebase Authentication checks
16
16
17
+
---
18
+
19
+
> **WARNING**: This branch is the work in progress for version 7 of AngularFire. [You can find version 6 here](https://github.com/angular/angularfire), if you're looking for documentation or to contribute to stable.
You can log [`screen_view` events](https://firebase.google.com/docs/reference/js/firebase.analytics.Analytics.html#parameters_10) yourself of course, but AngularFire provides the `ScreenTrackingService` which automatically integrates with the Angular Router to provide Firebase with screen view tracking. You simply can integrate like so:
Using the `CONFIG` DI Token (*default: {}*) will allow you to configure Google Analytics. E.g, you could skip sending the initial `page_view` event, anonymize IP addresses, and disallow ads personalization signals for all events like so:
Copy file name to clipboardExpand all lines: docs/auth/router-guards.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
`AngularFireAuthGuard` provides a prebuilt [`canActivate` Router Guard](https://angular.io/api/router/CanActivate) using `AngularFireAuth`. By default unauthenticated users are not permitted to navigate to protected routes:
With the exception of the Auth Emulator, the old way of setting the `host` and `port` for each emulator was done using a different set of tokens by passing the entire url path as string.
0 commit comments