Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Angular 7 Routes is not backward compatible, does not execute ** when it didn't match any route
See original GitHub issue🐞 bug report
Affected Package
The issue is caused by package @angular/....Is this a regression?
Yes, the previous version in which this bug was not present was: ....Description
A clear and concise description of the problem...🔬 Minimal Reproduction
https://stackblitz.com/...🔥 Exception or Error
🌍 Your Environment
Angular Version:
Anything else relevant?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Cannot match any routes - Stack Overflow
As far as I know this is not yet implemented in @angular/router and won't be because it will be replaced again. Adding it...
Read more >Add navigation with routing - Angular
The router is dedicated to routing and imported by the root AppModule . ... That doesn't match any existing route so the router...
Read more >Error: Cannot match any routes - Nishu Goel - Medium
In Angular, when working with routing, we face this error “Cannot match any routes” very commonly. This generally occurs when there is a...
Read more >Angular Navigation: How Routing & Redirects Work in Angular ...
The Angular Router is one of the most important libraries in an Angular application. Without it, apps would be single view/single context apps...
Read more >Routing in ASP.NET Core - Microsoft Learn
UseRouting(); // Location 2: after routing runs, endpoint will be non-null if routing found a match. app.Use(async (context, next) => { Console.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Several Project routes not work well after upgrade Angular from 6.3 to 7.2.9. const appRoutes: Routes = [ { path: ‘’, component: OverviewpublishedListComponent }, … { path: ‘**’, component: PageNavigateRouterComponent },
when it didn’t match any other route, it should execute the route as below: { path: ‘**’, component: PageNavigateRouterComponent },
but after upgrade to angular 7.2.9, it is not work again. Probably, this is extremly compatible issues. it already blocked the client correctly jump into the payment pages and so on. Now, it just jumps into the dashboard.
I try to know what had happened. I found the projects(upgraded angular 6.3 to 7.2.9 ) had been affected. In contrast, others( without upgrade angular from 6 to 7), the routes still work very well.
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.