Parent guard function is calling while a child guard function is pending result

Bug Report

Packages

“@angular/common”: “~9.1.12”, “@angular/compiler”: “~9.1.12”, “@angular/core”: “~9.1.12”, …

Description

I have next routes:

/nodes
/items
/items/subitems/:sid

Every route is routing module.

I have guards “canDeactivate” for items module and for /items/subitems/:sid module.

When I navigate in browser from /items/subitems/:sid to /nodes, Angular calls guards “canDeactivate”. The guard for /items/subitems/:sid returns Promise<boolean> result, so it’s asynchronous result and it’s pending, but after this guard, Angular calls /items guard.

Parent route (for /items) doesn’t have result from child guard (for /items/subitems/:sid), because it’s pending, but Angular calls it. It looks like a bug.

Should Angular call guard for /items while /items/subitems/:sid is pending?

[kbrilla]

This is working as intended. Please refer to #40577 and specifically #40577 (comment) if you have guards which are order-dependent.

Again Angular team is shuting down issue without reasoning why It is working this way and picking up discussion, even though we now have 20 upvotes rule - here the issue was up for one day? How could people even read issues before You take them down this way?

second thing it’s not a duplicate either as in mentioned issue there are multiple async guards in one node of routing and workaround is to use some hacky way with external que service or to separate those guards into separate empty string path nodes of routing and then It works fine. Here we already have multiple nodes so why CanDeactivate is working differently than all other guards and resolvers? And if there is a good reason mayby it’s not mentioned clearly in documentation, Also why not add option to change this behavior to match other guards?

Also new router mentioned would be great but looking at how typed forms are going we will wiat another 5 years minimum for it.

Please stop closing issues just beacause - this is so annoying.

[atscott]

This is working as intended. Please refer to https://github.com/angular/angular/issues/40577 and specifically https://github.com/angular/angular/issues/40577#issuecomment-768209703 if you have guards which are order-dependent.