So it took me a long time to get around to this, but I finally implemented the changes. A few issues persist: First, this fix loads "Prehistory" underneath "Home" whereas I wanted Prehistory to replace Home.
The second issue is that when you click on Prehistory and hover over the link, it prints out that the router parent is null. I was hoping to make it so that the router reflects the location where the user has navigated to--so if you're in Prehistory, the router reflects that, and its parent should be Home. Similarly if you were in a sub-section of Prehistory, like Prehumans, then the router's path would be to Prehuman, and its parent would be to Prehistory, and the parent of that would again be Home. I was told to use hash routes to try to accomplish this behavior, hence why my code had that before the fix. On Monday, September 24, 2018 at 2:07:05 AM UTC-4, Sander Elias wrote: > > Hi Admin, > > Here is a sample with an added router-outlet > <https://stackblitz.com/github/SanderElias/explain?file=src%2Fapp%2Fcomponents%2Fpages%2Fhome%2Fhome.component.html> > . > Also, I made a PR for your repo, so you can see the diff, and why the > stackBlitz didn't work for you. > > Regards > Sander > -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
