How to navigate relative from /questions/123/step1
to /questions/123/step2
within a component using Router
without string concatenation an
Note: the routes are case sensitive so make sure you match the casing across
This worked for me for Angular 8:
From the parent component / page, to navigate to the sub page using typescript:
this.router.navigate(['subPage'], { relativeTo: this.route });
My router in the parent's module looks like this:
const routes: Routes = [
{
path: '',
component: MyPage,
children: [
{ path: 'subPage', component: subPageComponent}
]
}
];
And on the parent's html page use the following to navigate using a link:
<a [routerLink]="'subPage'">Sub Page Link</a>
<router-outlet></router-outlet>
You may use below,
Assumption is questions
is loaded into your primary router-outlet
this.router.navigate([
'/',
{
outlets: {
primary: [
// below may be replaced with different variables
'questions',
'123',
'step2'
]
}
}
])
Hope this helps!!
First, inject router & ActivatedRoute on constructor
constructor(private route:ActivatedRoute,private router:Router) { }
then use to Click Event:
onEditClick(){
this.router.navigate(['edit'],{relativeTo:this.route});
You navigate to the expected page.In my scenario, I wanted to go recipe /1 to edit the recipe. http://localhost:4200/recipes/1/edit
After doing some more research I came across with
this.router.createUrlTree(['../step2'], {relativeTo: this.activatedRoute});
and
this.router.navigate(['../step2'], {relativeTo: this.activatedRoute});
First approach (Router.createUrlTree API) did not work for me, i.e. nothing happened. Second approach (Router.navigate API) works.
However, second approach uses NavigationExtras
(second argument) which is documented with @experimental
. Hopefully there won't be big changes with the next release again... and NavigationExtras
will be stable.
Any other suggestions/approaches, please do not hesitate to answer to my question above.
Update 2016-10-12
There is another stackoverflow question as well:
Update 2016-10-24
Documentation:
Update 2019-03-08
It seems that there were changes in Angular 7.1. There is an answer in another post how to solve it with Angular 7.1. Please refer to https://stackoverflow.com/a/38634440/42659.