Navigating to the same route not refreshing the component?

Question

I've upgraded to use the new Angular 2 router from router-deprecated and some behavior has changed.

The page I'm having issues with is a search page. We've chosen to put all the search terms in the URL using the HashLocationStrategy. The routes look like this:

const routes: RouterConfig = [
  { path: '', component: HomeComponent },
  { path: 'search/:term/:cat/:page/:sort/:size/:more', component: HomeComponent },
  { path: 'search/:term/:cat/:page/:sort/:size', component: HomeComponent },
  { path: 'search/:term/:cat/:page/:sort', component: HomeComponent },
  { path: 'search/:term/:cat/:page', component: HomeComponent },
  { path: 'search/:term/:cat', component: HomeComponent },
  { path: 'search/:term', component: HomeComponent },
  { path: 'details/:accountNumber', component: DetailsComponent }
];

I know a query string approach might be better fit for all these options but project requirements decided by other people...

Anyway if I navigate to localhost/#/search/Hello using this.router.navigate(['/search/Hello']); then the router works fine and everything is great. While on that page if I try to this.router.navigate(['/search/World']); then the URL in the browser's address bar will update accordingly but the component doesn't change at all.

Previously I could use routerCanReuse to indicate that I did want to reuse the search component and routerOnReuse would rerun the search when the navigation happened. I don't see equivalent's to these in @angular/router. How can I reload the current route with new URL parameters?

I'm running version 2.0.0-rc.3 for Angular 2 and 3.0.0-alpha.8 of @angular/router.

I am facing same problem.can you tell me where i can put this code on app.component.ts page or actual page(which is not getting reloaded). One more thing what is ** this.service.get(term).then(result => { console.log(result); });**. Can you explain in brief. — pushp
– pushp, Commented Jun 9, 2017 at 13:22

Doron Brikman · Accepted Answer · 2016-06-30 17:38:12Z

70

If only the params has changes the component itself won't be initialize again. But you can subscribe to changes in the parameters that you send.

For example on ngOnInit method you can do something like this:

ngOnInit() {
    this.sub = this.route.params.subscribe(params => {
       const term = params['term'];
       this.service.get(term).then(result => { console.log(result); });
     });
  }

answered Jun 30, 2016 at 17:38

Doron Brikman

2,5941 gold badge19 silver badges17 bronze badges

Sign up to request clarification or add additional context in comments.

10 Comments

Corey Ogburn Over a year ago

I was really curious why the params were an Observable. This explains it and makes a lot of sense.

Inigo Over a year ago

I don't understand this. The problem- or at least my problem- is that the ngOnInit function doesn't run again when the same route is called with a different parameter value. So what help is this...?

Doron Brikman Over a year ago

The idea is that angular don't need to mount the component again. Only the data has change, specifically the route data. So what you have is a function that will invoke anytime the route data changed and you can react to this change.

Lakshay Dulani Over a year ago

i got the point..subscribing to param value change..but there needs to be some other configuration needed too..i am subscribing to param change..but still the component is getting reloaded..

Daniel Kucal Over a year ago

@Lakshay google for custom route reuse strategy or check this answer

|

Mariia Bilyk · Accepted Answer · 2020-01-16 12:02:51Z

Probably, you don't need to run ngOnInit at all. And this is advantage of the angular router. What you can do is mentioned in the previous answer - subscribe to params or paramsMap (route.paramsMap: Observable<ParamMap> with Map interface).

There is another option - You can put your data retrieving to guard and re-run resolvers and guards on params change. Put runGuardsAndResolvers: 'paramsOrQueryParamsChange' in route configuration. Now it will be:

const routes: RouterConfig = [
{ 
     path: "search/:term/:cat/:page/:sort/:size/:more", 
     component: HomeComponent, 
     runGuardsAndResolvers: 'paramsOrQueryParamsChange' 
}, 
...];

Here you can find how to request data from api in resolvers.

Hey @Marria, route.paramsMap will only emit value on change in param. In my case, if I navigate to /path;param=1 again. Want this route.paramsMap to emit value again. I have also tried replaceUrl flag but it won't trigger on same route with same param ` this.router.navigate(['path', params], { replaceUrl: true });`

BatteryAcid · Accepted Answer · 2022-02-03 14:30:02Z

For later versions of Angular, using ActivatedRoute to subscribe to param changes provides a simple mechanism for refreshing data.

Quoted from answer by @Evgeny Nozdrev: https://stackoverflow.com/a/68503542/1956540

For URL params (like /persons/:id):

import { ActivatedRoute } from '@angular/router';

constructor(protected activeRoute: ActivatedRoute, ...) {
    this.activeRoute.paramMap.subscribe(paramMap => {
        const id = paramMap.get('id');    // get param from dictonary
        this.load(id);                    // load your data
    });
}

Lucian Bacila · Accepted Answer · 2021-04-05 12:24:36Z

-1

I faced the same problem and resolved this by making the router not to reuse the route. This can be done by writing this code in the constructor:

constructor(
    private router: Router,
) { 
    this.router.routeReuseStrategy.shouldReuseRoute = function () {
        return false;
    };
}

answered Apr 5, 2021 at 12:24

Lucian Bacila

135 bronze badges

1 Comment

Alvaro VS Over a year ago

Be careful. This will affect the Router component globally, and your internal router links will stop working.

Collectives™ on Stack Overflow

Navigating to the same route not refreshing the component?

4 Answers 4

10 Comments

1 Comment

Comments

1 Comment

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

10 Comments

1 Comment

Comments

1 Comment

Linked

Related