@angular/router

NavigationExtras

interface

Options that modify the Router navigation strategy. Supply an object containing any of these properties to a Router navigation function to control how the target URL should be constructed or interpreted.

interface NavigationExtras {
}

relativeTo

ActivatedRoute

Specifies a root URI to use for relative navigation.

For example, consider the following route configuration where the parent route has two children.

          
            [{  path: 'parent',  component: ParentComponent,  children: [{    path: 'list',    component: ListComponent  },{    path: 'child',    component: ChildComponent  }]}]

The following go() function navigates to the list route by interpreting the destination URI as relative to the activated child route

          
             @Component({...}) class ChildComponent {   constructor(private router: Router, private route: ActivatedRoute) {}   go() {     router.navigate(['../list'], { relativeTo: this.route });   } }

A value of null or undefined indicates that the navigation commands should be applied relative to the root.

queryParams

Params

Sets query parameters to the URL.

          
            // Navigate to /results?page=1router.navigate(['/results'], { queryParams: { page: 1 } });

fragment

string

Sets the hash fragment for the URL.

          
            // Navigate to /results#toprouter.navigate(['/results'], { fragment: 'top' });

queryParamsHandling

QueryParamsHandling

How to handle query parameters in the router link for the next navigation. One of:

preserve : Preserve current parameters.
merge : Merge new with current parameters.

The "preserve" option discards any new query params:

          
            // from /view1?page=1 to/view2?page=1router.navigate(['/view2'], { queryParams: { page: 2 },  queryParamsHandling: "preserve"});

The "merge" option appends new query params to the params from the current URL:

          
            // from /view1?page=1 to/view2?page=1&otherKey=2router.navigate(['/view2'], { queryParams: { otherKey: 2 },  queryParamsHandling: "merge"});

In case of a key collision between current parameters and those in the queryParams object, the new value is used.

preserveFragment

boolean

When true, preserves the URL fragment for the next navigation

          
            // Preserve fragment from /results#top to /view#toprouter.navigate(['/view'], { preserveFragment: true });

onSameUrlNavigation

OnSameUrlNavigation

How to handle a navigation request to the current URL.

This value is a subset of the options available in OnSameUrlNavigation and will take precedence over the default value set for the Router.

skipLocationChange

boolean

When true, navigates without pushing a new state into history.

          
            // Navigate silently to /viewthis.router.navigate(['/view'], { skipLocationChange: true });

replaceUrl

boolean

When true, navigates while replacing the current state in history.

          
            // Navigate to /viewthis.router.navigate(['/view'], { replaceUrl: true });

state

{ [k: string]: any; }

Developer-defined state that can be passed to any navigation. Access this value through the Navigation.extras object returned from the Router.getCurrentNavigation() method while a navigation is executing.

After a navigation completes, the router writes an object containing this value together with a navigationId to history.state. The value is written when location.go() or location.replaceState() is called before activating this route.

Note that history.state does not pass an object equality test because the router adds the navigationId on each navigation.

info

unknown

Use this to convey transient information about this particular navigation, such as how it happened. In this way, it's different from the persisted value state that will be set to history.state. This object is assigned directly to the Router's current Navigation (it is not copied or cloned), so it should be mutated with caution.

One example of how this might be used is to trigger different single-page navigation animations depending on how a certain route was reached. For example, consider a photo gallery app, where you can reach the same photo URL and state via various routes:

Clicking on it in a gallery view
Clicking
"next" or "previous" when viewing another photo in the album
Etc.

Each of these wants a different animation at navigate time. This information doesn't make sense to store in the persistent URL or history entry state, but it's still important to communicate from the rest of the application, into the router.

This information could be used in coordination with the View Transitions feature and the onViewTransitionCreated callback. The information might be used in the callback to set classes on the document in order to control the transition animations and remove the classes when the transition has finished animating.