CanMatch snapshot queryParams doesn't work

[ArielGueta]

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

router

Is this a regression?

No

Description

I want a sync access to router.snapshot.queryParams in CanMatch guard and it doesn't work:

{
          path: 'todos',
          canMatch: [() => {
            // the location is todos?foo=1
            console.log(inject(ActivatedRoute).snapshot.queryParams) // { }
            return true;
          }],
}

If I wrap it with a setTimeout it logs the correct value.

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

No response

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

No response

Anything else?

No response

[JoostK]

It seems illogical to me that ActivatedRoute would represent the route that is still being matched; it has not yet been activated so ActivatedRoute does not reflect the navigation that is being matched. The CanMatch functions are called with segments: UrlSegment[], is that what you're looking for?

[ArielGueta]

I understand what you're saying, but I expect at least to get access to the "current" activated route.

[atscott]

The current activated route is the current activated route. This is as @JoostK has described. Closing as working as intended.

FYI - you can get what you're looking for with inject(Router).getCurrentNavigation().initialUrl.queryParams

https://stackblitz.com/edit/angular-ivy-sgtr4a?file=src%2Fmain.ts,src%2Findex.html

[ArielGueta]

@atscott thanks! Can you please explain why it called twice, please?

[atscott]

@ArielGueta Yes. It's called twice because there are two stages at the beginning of the routing pipeline that need to call it. One which determines the final URL for the navigation (applyRedirects) and one that creates the ActivatedRouteSnapshots for the navigation (recognize). Both of these match the URL to the Route configs. I'm working on combining these two operations, but it's quite a long process that includes several breaking changes and is being done over the course of several major versions.

[ArielGueta]

Thanks!

[angular-automatic-lock-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.}