camaron is right. Your mistake is that you declare UtilityService twice: Once in the providers of SearchComponent. Once in the providers of TransferComponent. You should declare the service ONLY ONCE to make sure both components get the same instance. For this you can choose between either of these options: Declare the service in the providers … Read more
Updated for RC5 Instead of starting with the current URL and trying to get the routes from the URL, you can get all of the activated routes (associated with the primary outlet) from the RouterState: After the end of each successful navigation lifecycle, the router builds a tree of ActivatedRoutes, which make up the current … Read more
update Currently there is no automatic way. See also Angular 2 typescript error when using subscribe function on new router (rc 1) See also https://github.com/angular/angular/issues/6595#issuecomment-244232725 class MyAppComponent { constructor(router: Router) { router.events.subscribe(s => { if (s instanceof NavigationEnd) { const tree = router.parseUrl(router.url); if (tree.fragment) { // you can use DomAdapter const element = document.querySelector(“#” … Read more
So i was finally able to do this. The thing is Angular uses first match policy, so we need to match routes in a guard-type way, to be sure that right route with right module will be matched. First thing we need to add custom matchers for our routes which will only match them on … Read more
I was able to find a solution to my problem. You can make own custom url serializer by implementing the UrlSerializer class. Custom Url Serializer Create a custom url serializer like this: @Injectable() export class CustomUrlSerializer implements UrlSerializer { constructor(private defaultUrlSerializer: DefaultUrlSerializer){} parse(url: string): UrlTree { // Custom code here } serialize(tree: UrlTree): string { … Read more
update 2 That’s now fixed (Angular 2.3) for the new router by https://github.com/angular/angular/pull/13124 which allows to provide a custom reuse strategy. For an example see also https://www.softwarearchitekt.at/post/2016/12/02/sticky-routes-in-angular-2-3-with-routereusestrategy.aspx Angular docs https://angular.io/api/router/RouteReuseStrategy update 2 This answer is only for a long ago discontinued router version. See https://angular.io/docs/ts/latest/guide/router.html#!#guards for how to do it in the current router. original … Read more
Update: Sep 2019 As a few people have mentioned, the parameters in paramMap should be accessed using the common MapAPI: To get a snapshot of the params, when you don’t care that they may change: this.bankName = this.route.snapshot.paramMap.get(‘bank’); To subscribe and be alerted to changes in the parameter values (typically as a result of the … Read more
The code you are showing there is absolutely correct. I suspect that your problem is that you are not importing RouterModule (which is where RouterLink is declared) into the module which uses this template. I had a similar problem and it took me some time to solve as this step is not mentioned in the … Read more
In the new router (>= RC.3) https://angular.io/docs/ts/latest/api/router/index/Router-class.html resetConfig can be used router.resetConfig([ { path: ‘team/:id’, component: TeamCmp, children: [ { path: ‘simple’, component: SimpleCmp }, { path: ‘user/:name’, component: UserCmp } ] } ]); You might need to provide some dummy router configuration to not get errors on application startup. https://github.com/angular/angular/issues/11437#issuecomment-245995186 provides an RC.6 Plunker