-
Notifications
You must be signed in to change notification settings - Fork 24.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Router does not allow users to navigate to a route in the address bar unless a link is added some where in the page #8481
Comments
I'm running into a similar issue (new router in rc.1). |
Related to #8409 ? |
Me too |
We have an app with a page that has several components, and one of the children had a [routerLink] to open a specific component. It used to work fine with old router. After upgrading the app to RC.1, this page didn't render half of the components without reporting any errors. After we've added unneeded This is clearly a bug in the router. |
+1 - a lot of broken router features. |
I'm having the same problem. The routerLink doesn't even have to link to a valid route. It just has to exist. |
I'm able to remove the routerLinks all together if I inject Router into the top level app.component:
|
This issue was made obsolete by router v3: https://angularjs.blogspot.com/2016/06/improvements-coming-for-routing-in.html If you believe this is not the case, please file a new issue updating the description to router v3. thank you! |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
So i realized this, i have to add a router link to my page to get the routes to work.
<a [routerLink]="['/heroes']">Heroes</a>
Now if i type http://localhost:4200/heroes i actually get to the heroes page. If i remove the link from my page typing it in address bar does not load the route content.
Please refer to this thread
The text was updated successfully, but these errors were encountered: