15

NB. I've got a set of resulting from googling but, as I explain at the end, I sense that they aren't reliable, due to diversity.

I have two utility methods - one for navigating to the parent node and one for reloading self. The first one works as supposed to, while the other one fails to cause the reload.

navigateToParent(route: ActivatedRoute) {
  const options: NavigationExtras = { relativeTo: route };
  this.router.navigate([".."], options);
}

navigateToSelf(route: ActivatedRoute) {
  this.router.routeReuseStrategy.shouldReuseRoute = () => false;
  this.router.onSameUrlNavigation = "reload";
  const self = ".";
  this.router.navigate([self]);

  // const options: NavigationExtras = { relativeTo: route };
  // this.router.navigate(["."], options);
}

I followed the answer here, with the only exception that I'd like my path navigated to, to be generic, not hard-coded. I've tried passing different parameters, like self="." and self="" etc. Nothing seems to give me the desired reload.

What do I miss?

I also tried to pick the parts from the route passed into the service's method but I only see a bunch of observables, not the actual segments. And, of course, this.router.navigate(route) only caused an error.

Googling produced a lot of hints with vastly varying suggestions (e.g. this), which leads me to the suspicion that it might be heavily dependent on the version (I'm on 8.0) and, also, that many of the suggestions, although accepted, might be misleading and more harmful in the long run, without me realizing it.

Konrad Viltersten
  • 36,151
  • 76
  • 250
  • 438

8 Answers8

22

ok this next example works for me without reload the page:

on router component you have tu add 'onSameUrlNavigation' router.component:

@NgModule({
  imports: [RouterModule.forRoot(routes, { onSameUrlNavigation: 'reload' })],
  exports: [RouterModule],
})

now component you want reload

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

someFunction(){
  this.router.navigateByUrl('/route');
}
Flavien Volken
  • 19,196
  • 12
  • 100
  • 133
Gustavo Vzqm
  • 321
  • 2
  • 4
  • 1
    This is the best solution when using RouterModule.forChild(routes) which does not support the onSameUrlNavigation option. – Lars H Jan 07 '21 at 21:23
  • this is a good solution but seems to be marking a whole bunch of other links as active ever since I've had it enabled – Anon May 10 '22 at 06:49
  • Awesome, thank you! This solution works for Angular 13 – Carlo Nyte Nov 03 '22 at 05:18
14

You can find total working example here in this StackBlitz Link

Update First of all doing window.location.reload() is totally against of Single-Page-Application nature. rather, You can reload particular component when actually clicking on that link.. so, to do this task we have angular router. For particular component reload you can push this line of code in main app.component.ts once for full application.

mySubscription;

 constructor(private router: Router, private activatedRoute: ActivatedRoute){
    this.router.routeReuseStrategy.shouldReuseRoute = () => false;
    this.mySubscription = this.router.events.subscribe((event) => {
      if (event instanceof NavigationEnd) {
         // Trick the Router into believing it's last link wasn't previously loaded
         this.router.navigated = false;
      }
    }); 
 }

above code we are going to subscribing to router-events. and then we are checking each and every router-NavigationEnd event, then just telling router, forget to add current navigation of router to its own history. So, each time whenever we are trying to reload same component each and every events are firing for that particular component only, thats a SPA.

IN app.component.ts of ngOnDestroy() we have to unsubscribe from router events, when component is destroyed.

ngOnDestroy(){
  if (this.mySubscription) {
    this.mySubscription.unsubscribe();
  }
}

Now, for example you have Home and Details component or anything else of component... You can reload each component by calling this.router.navigate([this.router.url]) this will reload all current component. for example, In home component we have reload-button and click event of that we are just calling this.router.navigate([this.router.url]). same for details component too.. or any other component..

Home.component.ts

reLoad(){
  this.router.navigate([this.router.url])
}

Details.component.ts

reLoad(){
  this.router.navigate([this.router.url])
}

You can check in updated above StackBlitz link, all working example of reloading with full router-state reloading. In browser console see each and every events of component is firing by clicking button reload().

Flavien Volken
  • 19,196
  • 12
  • 100
  • 133
Developer
  • 3,309
  • 2
  • 19
  • 23
  • I don't fully grasp the idea. I don't even have a */home* path in my project. And I'd like to understand what I did wrong in my original approach and how to resolve that. As far I understand your example, you navigate to a hard-coded URL, aren't you? Please elaborate. – Konrad Viltersten Jan 01 '20 at 19:24
  • Here main approach is `skipLocationChange` to reload already activated route. As I think it's your main problem to do. I showed you one demo, you can use this approach in your use-case. If possible make your stackblitz and share link to help you more. – Developer Jan 01 '20 at 19:35
  • Why do we need `ngOnDestroy()` here since this is the Root component and it will never destroy? – Sampath Jul 11 '20 at 19:12
  • After adding this.router.navigated = false the menu items do not highlighted properly for me. So I switched to Gustavo's solution. – Peter Ambruzs Mar 21 '22 at 09:15
4

on your app-routing-module.ts pls verify you have the {onSameUrlNavigation: 'reload'}

@ngModule({
 imports: [RouterModule.forRoot(routes, {onSameUrlNavigation: 'reload'})],
 exports: [RouterModule],
 })
Shankarlal D
  • 169
  • 1
  • 7
1

Try the following:

imports: [RouterModule.forRoot(routes, { onSameUrlNavigation: 'reload' })]
Kevy Granero
  • 643
  • 5
  • 17
Reshan Maduka
  • 281
  • 2
  • 5
0
public routerreuse: any;

ngOnInit(): void {
    this.routerreuse = this._router.routeReuseStrategy.shouldReuseRoute;
    this._router.routeReuseStrategy.shouldReuseRoute = (future: ActivatedRouteSnapshot, curr: ActivatedRouteSnapshot) => {
      return (curr != this.route.snapshot)
    };
}
   
ngOnDestroy(): void {
    this._router.routeReuseStrategy.shouldReuseRoute = this.routerreuse;
}

this should work when the same route url is changing with browser back in history. It reloads only the same content with the same route

dev.ws
  • 89
  • 4
-2
<button type="button" mat-raised-button color="warn" onclick="window.location.reload();">

Window.location.reload() on Button onClick property

rajquest
  • 535
  • 1
  • 5
  • 10
-3

Try the following.

this.ngOnInit();

It works for me with same route reload.

Konrad Viltersten
  • 36,151
  • 76
  • 250
  • 438
  • 3
    This is not reLoad() of page() or component. By calling ngOnInit() by yourself, it will not called all life-cycle methods, rather you are only calling just one ngOnInt(). so this is not good practice to call ngOnInit() by yourself for complete reLoad of page. – Developer Jan 02 '20 at 07:34
  • The code isn't executed in the component itself. It's done in the service. And the extra thing is that I don't know which component that's supposed to be reloaded at that certain moment. At the moment, the user needs to hit F5 to reload the window (upon which, the correct state and data is loaded as supposed to). I only want to emulate the reloading. At least at the moment. – Konrad Viltersten Jan 02 '20 at 08:17
-3

To Reload the same page...Try This

window.location.reload();
Iliyas Shaik
  • 108
  • 5