Angular 2 router fails to reuse same Component instance when navigating to same route with different params

Question

By default, the router reuses a component instance when it re-navigates to the same component type without visiting a different component first. The parameters can change between each re-use

I need help figuring out why this does not work on my lazy-loaded routes. To reproduce:

Open this plunker
On LazyLoadedComponent press Next ID button to trigger navigation to the same route (new param). Notice that the component is destroyed and a new instance is initialized each time.

On HomeComponent, things work as expected. Triggering navigation executes the ActivatedRoute.params.subscribe() callback but the component is not re-initialized

I'm using Angular 2 rc.5 and Angular Router 3 rc.1 Why does my lazy-loaded component not behave in accordance with the docs?

BeetleJuice · Accepted Answer · 2016-08-22 21:46:42Z

1

This is an Angular bug. It has been reported and the next version should be fixed. See https://github.com/angular/angular/pull/10707

answered Aug 22, 2016 at 21:46

BeetleJuice

41.1k24 gold badges119 silver badges181 bronze badges

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

Collectives™ on Stack Overflow

Angular 2 router fails to reuse same Component instance when navigating to same route with different params

1 Answer 1

Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Related