fix(angular): Handle routes with empty path

[de-don]

Update function getParameterizedRouteFromSnapshot to handle routes with empty paths.

Fixes GH-7681

Before submitting a pull request, please take a look at our
Contributing guidelines and verify:

• [+] If you've added code that should be tested, please add tests.
• [+] Ensure your code lints and the test suite passes (yarn lint) & (yarn test).

[Lms24]

Hey @de-don, thanks for opening this PR!

This fix generally LGTM so I hope we can get it in soon. Can you please tell us with which Angular version you tested this change? Since we support Angular 10 to 15, we should make sure we tested it at least in NG10 and NG15.

[de-don]

Hey @de-don, thanks for opening this PR!

This fix generally LGTM so I hope we can get it in soon. Can you please tell us with which Angular version you tested this change? Since we support Angular 10 to 15, we should make sure we tested it at least in NG10 and NG15.

I have tested this code on my project with Angular 15, and as I checked, tests in repo check this code with Angular 10.

The main idea of this code, that we should proceed with path: "", but old code stops on this value. No new/old feature used in my changes.

[Lms24]

Thanks for your response @de-don! I have just tested this in NG10 and it still seems to work. Will ✅ and merge soon. Thanks again for contributing!

I have tested this code on my project with Angular 15, and as I checked, tests in repo check this code with Angular 10.

FYI, technically, that's true but the routing instrumentation is unit-tested without Angular's testbed/testing environment. It just unit-tests the getParameterizedRouteFromSnapshot function. This isn't great obviously but at the moment we don't have the resources to improve Angular tests. In the long-run, I'd like to create e2e/integration tests, like we have for NextJS or Remix for example. This way, we can just ensure that we actually send the correct stuff. Let's see when we get to it.