How to handle query parameters in angular 2 How to handle query parameters in angular 2 javascript javascript

How to handle query parameters in angular 2


RouteParams are now deprecated , So here is how to do it in the new router.

this.router.navigate(['/login'],{ queryParams: { token:'1234'}})

And then in the login component you can take the parameter,

constructor(private route: ActivatedRoute) {}ngOnInit() {    // Capture the token  if available    this.sessionId = this.route.queryParams['token']}

Here is the documentation


To complement the two previous answers, Angular2 supports both query parameters and path variables within routing. In @RouteConfig definition, if you define parameters within a path, Angular2 handles them as path variables and as query parameters if not.

Let's take a sample:

@RouteConfig([  { path: '/:id', component: DetailsComponent, name: 'Details'}])

If you call the navigate method of the router like this:

this.router.navigate( [  'Details', { id: 'companyId', param1: 'value1'}]);

You will have the following address: /companyId?param1=value1. The way to get parameters is the same for both, query parameters and path variables. The difference between them is that path variables can be seen as mandatory parameters and query parameters as optional ones.

Hope it helps you,Thierry

UPDATE: After changes in router alpha.31 http query params no longer work (Matrix params #2774). Instead angular router uses so called Matrix URL notation.

Reference https://angular.io/docs/ts/latest/guide/router.html#!#optional-route-parameters:

The optional route parameters are not separated by "?" and "&" as they would be in the URL query string. They are separated by semicolons ";" This is matrix URL notation — something you may not have seen before.


It seems that RouteParams no longer exists, and is replaced by ActivatedRoute. ActivatedRoute gives us access to the matrix URL notation Parameters. If we want to get Query string ? paramaters we need to use Router.RouterState. The traditional query string paramaters are persisted across routing, which may not be the desired result. Preserving the fragment is now optional in router 3.0.0-rc.1.

import { Router, ActivatedRoute } from '@angular/router';@Component ({...})export class paramaterDemo {  private queryParamaterValue: string;  private matrixParamaterValue: string;  private querySub: any;  private matrixSub: any;  constructor(private router: Router, private route: ActivatedRoute) { }  ngOnInit() {    this.router.routerState.snapshot.queryParams["queryParamaterName"];    this.querySub = this.router.routerState.queryParams.subscribe(queryParams =>       this.queryParamaterValue = queryParams["queryParameterName"];    );    this.route.snapshot.params["matrixParameterName"];    this.route.params.subscribe(matrixParams =>      this.matrixParamterValue = matrixParams["matrixParameterName"];    );  }  ngOnDestroy() {    if (this.querySub) {      this.querySub.unsubscribe();    }    if (this.matrixSub) {      this.matrixSub.unsubscribe();    }  }}

We should be able to manipulate the ? notation upon navigation, as well as the ; notation, but I only gotten the matrix notation to work yet. The plnker that is attached to the latest router documentation shows it should look like this.

let sessionId = 123456789;let navigationExtras = {  queryParams: { 'session_id': sessionId },  fragment: 'anchor'};// Navigate to the login page with extrasthis.router.navigate(['/login'], navigationExtras);