From 92e131ea53fea32ab4ca91632c08cf36e8cd88de Mon Sep 17 00:00:00 2001 From: Joey Date: Wed, 10 Feb 2021 21:44:43 +0800 Subject: [PATCH] docs: fix navigation-failures type count (#767) Co-authored-by: xiaaa123 <3288432965@qq.com> --- docs/guide/advanced/navigation-failures.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guide/advanced/navigation-failures.md b/docs/guide/advanced/navigation-failures.md index e9247c33..54f34b61 100644 --- a/docs/guide/advanced/navigation-failures.md +++ b/docs/guide/advanced/navigation-failures.md @@ -59,7 +59,7 @@ If you omit the second parameter: `isNavigationFailure(failure)`, it will only c ## 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 four different types: +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: - `aborted`: `false` was returned inside of a navigation guard to the navigation. - `cancelled`: A new navigation took place before the current navigation could finish. e.g. `router.push` was called while waiting inside of a navigation guard. -- 2.47.3