Tel Map


Angular2 RC3 Router

Some days ago, the new Angular2 RC3 release candidate (and also some days earlies RC2) has been released. Again, some changes were made to the Angular2 structure that everyone needs to update in their Angular2 applications to become compatible to the new version. I want to show some of the changes in the new Angular2 RC3 Router in this article.

Angular2 RC3 Router

After the Angular2 Beta Router and the new Router introduced in RC0, yet another Router package has been released and the old one has bee deprecated (and is now still available as package @angular/router-deprecated version 2.0.0-rc.2). According to the team, the new router was necessary to handle some fundamental problems with the previous routing mechanism, which might be working correctly with 90%ish of the use cases, but was not able to handle all use cases Angular2 wants to address.

Although the new router package is official still in Alpha, it has been announced by the Angular2 team, that the new Router package should already be used instead of the old package.

Include the new Dependency

To upgrade Angular2 from the old RC0/1/2 versions to RC3, you upgrade the package version of the Angular packages to 2.0.0-rc.3. Because of the unregular Router upgrades, the Angular2 team has decided to use a different release cycle for the Router than for the rest of Angular2, so the current version is “3.0.0-alpha.7“:

Define routes

In the Router Version2 the routes were defined by the @Routes annotation on the application component, which contained an Array of all paths with corresponding Component.

In the new Version3 Router, the routes already have to be given as dependency to the bootstrap process.

In the easiest configuration the routes also contain just a path (buth now without leading slash!) and a component. It is recommended to bundle the routes into a single Typescript file:

Similar to the previous router, the definitions allow path paramaters beginning with a colon (like “baz/:id” can match “baz/123“). These path parameters can later be used in the target component e.g. to load a specific dataset with a given id.

Instead of listing all routes in a plain list, routes can contain sub-routes by defining the “children” attribute. Those child-routes are then appended to the prefix defined by the parent route, like this

Placing the Router Outlet

This part works exactly than in the V2 Router: To tell the Router where to include the currently activated Component, a special Tag

has to be placed somewhere in the template of the application. Whenever a route is selected, the corresponding component will be embedded inside this tag.

There are more advanced setups, which can include secondary router outlets, e.g. for a sidebar or an overview. For this the outlet has to be given a name attribute, and also the routes for this outlet has to declare the same name as “outlet” attribute.

Placing Router Links

In order to navigate from one route to an other, you have to place special routerLink attributes in your template, e.g. in buttons or hyperlinks. To use this directive, you need to import and provide “ROUTER_DIRECTIVES” in the corresponding components (like in the V2 Router):

Like real URLs, the routerlinks can be either absolute paths and match a complete route from the beginning, or relative paths, which will match a route relative to the current route, e.g.

Path parameters

In order to parse the given path parameters (e.g. to get the “123” from the route “baz/123“), the component can declare the dependency “ActivatedRoute” to get the parameters. In difference to the RC2 router, the parameters can not be evaluated directly, but are instead given as Observable. When a route is changed but still uses the same Component (e.g. link from “baz/123” to “baz/456“), the component is not recreated, but instead only the ActivatedRoute parameters given as Obserables publish a new value.

In the official documentation it is recommended to create a subscription in the ngOnInit method and unsubscribe in the ngOnDestroy method to prevent a memory leak.

2 Replies to “Angular2 RC3 Router”

  1. That’s weird! In previous versions you could name a route, so that you could have same parameters to different routes, like:

    path: ‘:categoryUrl’, name: ‘Category’, component: CategoryComponent -> [routerLink]=”[‘/Category’, { categoryUrl: categoryUrl.url }]”

    path: ‘:categoryUrl’, name: ‘Product’, component:ProductComponent -> [routerLink]=”[‘/Product’, { categoryUrl: categoryUrl.url }]”

    Both routes have the same parameter and I can say which component I want to hit. Is it possible to keep doing that in RC3? I really tried but with no success.

Leave a Reply

Your email address will not be published. Required fields are marked *