Angular 6 path params issues
up vote
0
down vote
favorite
Below is the issue which I am encountering when I use children route to move to edit-todo page driven by Todo component, using angular 6.
When I nest the path as children like below, I am not able to get value of :id
{ path: 'edit-todo', component: EditTodoComponent, children:[
{path: ':id', component: EditTodoComponent}
]},
console.log(activatedRoute.snapshot.url);
When separate the route I am able to get the value of id.
{ path: 'edit-todo', component: EditTodoComponent},
{ path: 'edit-todo/:id', component: EditTodoComponent },
console.log(activatedRoute.snapshot.url);
Is it possible to get the value of ID using the children array shown in approach 1.
angular angular-ui-router
edited Nov 19 at 19:38
Claies
19.5k33363
asked Nov 19 at 16:55
sachin bhat
143
add a comment |
up vote
0
down vote
favorite
Below is the issue which I am encountering when I use children route to move to edit-todo page driven by Todo component, using angular 6.
When I nest the path as children like below, I am not able to get value of :id
{ path: 'edit-todo', component: EditTodoComponent, children:[
{path: ':id', component: EditTodoComponent}
]},
console.log(activatedRoute.snapshot.url);
When separate the route I am able to get the value of id.
{ path: 'edit-todo', component: EditTodoComponent},
{ path: 'edit-todo/:id', component: EditTodoComponent },
console.log(activatedRoute.snapshot.url);
Is it possible to get the value of ID using the children array shown in approach 1.
angular angular-ui-router
edited Nov 19 at 19:38
Claies
19.5k33363
asked Nov 19 at 16:55
sachin bhat
143
The first approach doesn't make much sense. Why would you display an EditTodo component inside another EditTodo component?
– JB Nizet
Nov 19 at 20:51
have you added the module that haseditTodoComponentin theapp-routing.module.ts? Also i agree with @JBNizet here .
– CruelEngine
Nov 20 at 4:57
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Below is the issue which I am encountering when I use children route to move to edit-todo page driven by Todo component, using angular 6.
When I nest the path as children like below, I am not able to get value of :id
{ path: 'edit-todo', component: EditTodoComponent, children:[
{path: ':id', component: EditTodoComponent}
]},
console.log(activatedRoute.snapshot.url);
When separate the route I am able to get the value of id.
{ path: 'edit-todo', component: EditTodoComponent},
{ path: 'edit-todo/:id', component: EditTodoComponent },
console.log(activatedRoute.snapshot.url);
Is it possible to get the value of ID using the children array shown in approach 1.
angular angular-ui-router
edited Nov 19 at 19:38
Claies
19.5k33363
asked Nov 19 at 16:55
sachin bhat
143
Below is the issue which I am encountering when I use children route to move to edit-todo page driven by Todo component, using angular 6.
When I nest the path as children like below, I am not able to get value of :id
{ path: 'edit-todo', component: EditTodoComponent, children:[
{path: ':id', component: EditTodoComponent}
]},
console.log(activatedRoute.snapshot.url);
When separate the route I am able to get the value of id.
{ path: 'edit-todo', component: EditTodoComponent},
{ path: 'edit-todo/:id', component: EditTodoComponent },
console.log(activatedRoute.snapshot.url);
Is it possible to get the value of ID using the children array shown in approach 1.
angular angular-ui-router
angular angular-ui-router
edited Nov 19 at 19:38
Claies
19.5k33363
asked Nov 19 at 16:55
sachin bhat
143
edited Nov 19 at 19:38
Claies
19.5k33363
asked Nov 19 at 16:55
sachin bhat
143
edited Nov 19 at 19:38
Claies
19.5k33363
edited Nov 19 at 19:38
Claies
19.5k33363
edited Nov 19 at 19:38
Claies
19.5k33363
19.5k33363
asked Nov 19 at 16:55
sachin bhat
143
asked Nov 19 at 16:55
sachin bhat
143
asked Nov 19 at 16:55
sachin bhat
143
143
The first approach doesn't make much sense. Why would you display an EditTodo component inside another EditTodo component?
– JB Nizet
Nov 19 at 20:51
have you added the module that haseditTodoComponentin theapp-routing.module.ts? Also i agree with @JBNizet here .
– CruelEngine
Nov 20 at 4:57
add a comment |
The first approach doesn't make much sense. Why would you display an EditTodo component inside another EditTodo component?
– JB Nizet
Nov 19 at 20:51
have you added the module that haseditTodoComponentin theapp-routing.module.ts? Also i agree with @JBNizet here .
– CruelEngine
Nov 20 at 4:57
The first approach doesn't make much sense. Why would you display an EditTodo component inside another EditTodo component?
– JB Nizet
Nov 19 at 20:51
The first approach doesn't make much sense. Why would you display an EditTodo component inside another EditTodo component?
– JB Nizet
Nov 19 at 20:51
have you added the module that has
editTodoComponent in the app-routing.module.ts ? Also i agree with @JBNizet here .– CruelEngine
Nov 20 at 4:57
have you added the module that has
editTodoComponent in the app-routing.module.ts ? Also i agree with @JBNizet here .– CruelEngine
Nov 20 at 4:57
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53379331%2fangular-6-path-params-issues%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The first approach doesn't make much sense. Why would you display an EditTodo component inside another EditTodo component?
– JB Nizet
Nov 19 at 20:51
have you added the module that has
editTodoComponentin theapp-routing.module.ts? Also i agree with @JBNizet here .– CruelEngine
Nov 20 at 4:57