From c443de4217c0fefec48f6f8bbcc5a4fc9921b5d2 Mon Sep 17 00:00:00 2001 From: Eduardo San Martin Morote Date: Fri, 30 Jun 2023 13:54:41 +0200 Subject: [PATCH] docs: global navigation failures Close #1905 --- packages/docs/guide/advanced/navigation-failures.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/packages/docs/guide/advanced/navigation-failures.md b/packages/docs/guide/advanced/navigation-failures.md index b299075a..cc76a38d 100644 --- a/packages/docs/guide/advanced/navigation-failures.md +++ b/packages/docs/guide/advanced/navigation-failures.md @@ -62,6 +62,18 @@ if (isNavigationFailure(failure, NavigationFailureType.aborted)) { If you omit the second parameter: `isNavigationFailure(failure)`, it will only check if `failure` is a _Navigation Failure_. ::: +## Global navigation failures + +You can detect global navigation failures globally by using the [`router.afterEach()` navigation guard](./navigation-guards.md#global-after-hooks): + +```ts +router.afterEach((to, from, failure) => { + if (failure) { + sendToAnalytics(to, from failure) + } +}) +``` + ## Differentiating Navigation Failures As we said at the beginning, there are different situations aborting a navigation, all of them resulting in different _Navigation Failures_. They can be differentiated using the `isNavigationFailure` and `NavigationFailureType`. There are three different types: -- 2.47.2