runGuardsAndResolvers documentation doesn’t clearly describe when it’s used

Which @angular/* package(s) are the source of the bug?

router

Is this a regression?

No

Description

The Documentation suggests that you can supply a function to runGuardsAndResolvers . The link will take you to the documentation where it gives the type.

So I supplied the following and saw that not only was my route guard still being run, but the console log was not output.

((from: ActivatedRouteSnapshot, to: ActivatedRouteSnapshot) => {
          console.log(from,to);

          return false;
})

It seems something is not working as described in the documentation. So either it’s a bug or the documentation is misleading?

Please provide a link to a minimal reproduction of the bug

I don’t have time to do this. I’ll figure out another solution if needed.

Please provide the exception or error you saw

There were no errors. The guards ran when they should not have.

Please provide the environment you discovered this bug in (run ng version)

Angular CLI: 13.2.6
Node: 16.14.0
Package Manager: npm 8.3.1
OS: win32 x64

Angular: 13.2.7
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1302.6
@angular-devkit/build-angular   13.2.6
@angular-devkit/core            13.2.6
@angular-devkit/schematics      13.2.6
@angular/cdk                    13.3.6
@angular/cli                    13.2.6
@angular/flex-layout            13.0.0-beta.38
@angular/material               13.3.6
@schematics/angular             13.2.6
rxjs                            7.5.5
typescript                      4.5.5

Anything else?

I have seen runGuardsAndResolvers work in an older version of angular, but it was about a year and a half ago since I implemented that and it was for a different website.

[atscott]

This is an issue with the documentation. RunGuardsAndResolvers only applies when the navigation doesn’t change the activated route. Probably would have been better named “rerunGuardsAndResolvers”.

That is, it applies only when they would otherwise not be run because the route isn’t being activated or deactivated.

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}