The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

507205 (2) [Avatar] Offline
#1
Section 6.2 mentions that a component can be removed from the dom due to navigation. I would like to understand this better? In my use case, I have a listing page and a detail page and need to navigate back and forth between the pages (standard stuff). I think I would like to keep the listing page in the dom and let a websocket update the listing page. But I'm seeing that navigation is causing the listing page's constructor to get invoked when I navigated back to it from the detail page. Can I prevent this?

BTW, I ran the routing example from section 3.1 in Plunker (https://plnkr.co/edit/yjRrZeWffpk5GlKnZP82?p=info) and it worked as expected. Upon navigation between the HomeComponent and ProductDetailComponent, I do see the HomeComponent's constructor reloading, which I assume means the dom is being reloaded.
Yakov Fain (219) [Avatar] Offline
#2
If you keep your master and detail routes open at the same time, the detail route won't be reloaded. Take a look at this app: https://github.com/Farata/angulartypescript/tree/master/chapter5/observables/src/app/master-detail