Version 6 of Angular Now Available!Learn MoreHome
Features
Resources
Events
Blog
Getting Started
1. Introduction
2. The Application Shell
3. The Hero Editor
4. Displaying a List
5. Master/Detail Components
6. Services
7. Routing
8. HTTP
Architecture Overview
Intro to Modules
Intro to Components
Intro to Services and DI
Next Steps
Displaying Data
Template Syntax
User Input
Lifecycle Hooks
Component Interaction
Component Styles
Angular Elements
Dynamic Components
Attribute Directives
Structural Directives
Pipes
Forms Overview
Reactive Forms
Template-driven Forms
Form Validation
Dynamic Forms
Observables
The RxJS Library
Observables in Angular
Practical Usage
Compare to Other Techniques
Bootstrapping
NgModules Introduction
JS Modules vs NgModules
Frequently Used NgModules
Types of Feature Modules
Entry Components
Feature Modules
Providers
Singleton Services
Lazy Loading Feature Modules
Sharing NgModules
NgModule API
NgModule FAQs
Angular Dependency Injection
Hierarchical Injectors
DI Providers
DI in Action
Navigate the Component Tree
HttpClient
Routing & Navigation
Introduction
Transition and Triggers
Complex Sequences
Reusable Animations
Route Transition Animations
Testing
Cheat Sheet
Internationalization (i18n)
Language Service
Security
Setup for local development
Anatomy of the Setup
Browser Support
Npm Packages
TypeScript Configuration
Ahead-of-Time Compilation
Deployment
Introduction
Getting Started
Service Worker Communication
Service Worker in Production
Service Worker Configuration
Updating Your Projects
Angular Releases
Upgrading Instructions
Upgrading for Performance
AngularJS-Angular Concepts
Server-side Rendering
Visual Studio 2015 QuickStart
Style Guide
Glossary
API
This is the archived documentation for Angular v6. Please visit angular.io to see documentation for the current version of Angular.
mode_edit code
API > @angular/router

RouterLinklink

  • NgModule
  • Selectors
  • Properties
  • Description
  • Methods
  • onClick()

Lets you link to specific routes in your app.

See more...

NgModulelink

  • RouterModule
          
          RouterModule
        

Selectorslink

  • :not(a)[routerLink]

Propertieslink

Property Description
@Input()
queryParams: { [k: string]: any; }
@Input()
fragment: string
@Input()
queryParamsHandling: QueryParamsHandling
@Input()
preserveFragment: boolean
@Input()
skipLocationChange: boolean
@Input()
replaceUrl: boolean
@Input()
routerLink: any[] | string
Write-only.
@Input()
preserveQueryParams: boolean
Write-only.
urlTree: UrlTree Read-only.

Descriptionlink

Consider the following route configuration: [{ path: 'user/:name', component: UserCmp }]. When linking to this user/:name route, you use the RouterLink directive.

If the link is static, you can use the directive as follows: <a routerLink="/user/bob">link to user component</a>

If you use dynamic values to generate the link, you can pass an array of path segments, followed by the params for each segment.

For instance ['/team', teamId, 'user', userName, {details: true}] means that we want to generate a link to /team/11/user/bob;details=true.

Multiple static segments can be merged into one (e.g., ['/team/11/user', userName, {details: true}]).

The first segment name can be prepended with /, ./, or ../:

  • If the first segment begins with /, the router will look up the route from the root of the app.
  • If the first segment begins with ./, or doesn't begin with a slash, the router will instead look in the children of the current activated route.
  • And if the first segment begins with ../, the router will go up one level.

You can set query params and fragment as follows:

<a [routerLink]="['/user/bob']" [queryParams]="{debug: true}" fragment="education"> link to user component </a>
      
      <a [routerLink]="['/user/bob']" [queryParams]="{debug: true}" fragment="education">
  link to user component
</a>
    

RouterLink will use these to generate this link: /user/bob#education?debug=true.

(Deprecated in v4.0.0 use queryParamsHandling instead) You can also tell the directive to preserve the current query params and fragment:

<a [routerLink]="['/user/bob']" preserveQueryParams preserveFragment> link to user component </a>
      
      <a [routerLink]="['/user/bob']" preserveQueryParams preserveFragment>
  link to user component
</a>
    

You can tell the directive to how to handle queryParams, available options are:

  • 'merge': merge the queryParams into the current queryParams
  • 'preserve': preserve the current queryParams
  • default/'': use the queryParams only

Same options for NavigationExtras#queryParamsHandling.

<a [routerLink]="['/user/bob']" [queryParams]="{debug: true}" queryParamsHandling="merge"> link to user component </a>
      
      <a [routerLink]="['/user/bob']" [queryParams]="{debug: true}" queryParamsHandling="merge">
  link to user component
</a>
    

The router link directive always treats the provided input as a delta to the current url.

For instance, if the current url is /user/(box//aux:team).

Then the following link <a [routerLink]="['/user/jim']">Jim</a> will generate the link /user/(jim//aux:team).

See createUrlTree for more information.

Methodslink

onClick() link

mode_edit code
onClick(): boolean
      
      onClick(): boolean
    

Parameters

There are no parameters.

Returns

boolean

Resources

  • About
  • Resource Listing
  • Press Kit
  • Blog

Help

  • Stack Overflow
  • Gitter
  • Report Issues
  • Code of Conduct

Community

  • Events
  • Meetups
  • Twitter
  • GitHub
  • Contribute

Languages

  • 中文版
  • 日本語版

Powered by Google ©2010-2018. Code licensed under an MIT-style License. Documentation licensed under CC BY 4.0.

Version 6.1.11-build.55581+sha.79fb9d4.