-
Notifications
You must be signed in to change notification settings - Fork 12k
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
ng generate route <name> created scaffolds not working. #989
Comments
@UzairNouman that's odd. Can you give me exact reproduction steps that I can follow so I can debug it? |
Yeah,that's too odd.Maybe I am missing something. 1-is to make changes to main component 2-make changes to the Route Component
3-Create
You may have noticed |
I am experiencing this too, I don't know, but perhaps it's something with the way angular-cli serves the files? I don't really know |
@graknol I had the same issue and this
fixed it. The router is broken in RC1 has breaking changes. |
angular-cli is using '@angular/router', @fadeojo can you tell me how you are using '@angular/router-deprecated'? |
@UzairNouman try npm installing |
@UzairNouman the router has breaking changes for RC1. https://github.com/angular/angular/blob/master/CHANGELOG.md |
Here are some bug reports on the main repository that might help till it gets fixed. |
Thanks @planser,your suggestion solved the issue. |
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. |
I created the routes with angular cli, it created all the scaffolds and necessary references in the parent component :
@Routes([ {path: '/hero', component: HeroComponent} ])
Also added the router outlet tag in the parent component's HTML template.Everything seems fine but still when i try to access that route,I see the parent template outputting but component whose template has to be resolved in the router outlet tag is not visible.
Although when I tried to make the project folder with npm as guided in the official angular docs,route works fine.
The text was updated successfully, but these errors were encountered: