-
Notifications
You must be signed in to change notification settings - Fork 138
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
Relative child-routing #16
Comments
I just checked the plunker and it actually does use relative links: https://plnkr.co/edit/1wB5QZSPvvCJZXBWMLXU?p=preview
<li *ngFor="let person of people">
<a uiSref=".person" [uiParams]="{ personId: person.id }">
{{person.name}}
</a>
</li> What troubles are you having? |
I have to use people.person, or it simply won't work. My biggest problem right now though, which may make me return to regular Angular 2 routing, is that the angular cli can't compile with the UIRouter.ForRoot() line in there. If I add it back after ng serve it runs fine. Also, when I enter a route in the address bar, it doesn't work. Only the routing through uiSref links works at the moment. Presumably I'm overlooking something. |
HI! Try this temporary solution for Angular cli #13 |
@niwrA you should try this in your UI Router Config
|
There is now a nontrivial sample app built with the Angular-CLI. |
Thank You very much for your work, @christopherthielen! |
The tutorial ends with suggesting that you can use .person instead of people.person for relative addressing. I could not get this to work however (it works otherwise). Is that a bug? Or am I just missing something?
The text was updated successfully, but these errors were encountered: