Sibling Outlet Issues

[weasnerb]

I have almost completed setting up a hybrid application and wanted to see what sibling router outlets would look like so that when I am converting some page level components I can have angular's router take care of routing for me. My issue is that angular is not recognizing routes and injecting its components into the dom when it should.

I have been following the article from Nrwl here: https://blog.nrwl.io/upgrading-angular-applications-managing-routers-and-url-ca5588290aaa

I have 2 examples with the angular phonecat hybrid application using the strategies they suggest:

• https://github.com/weasnerb/angular-phonecat-migration/tree/siblingRoutesHandlingStrategy
• https://github.com/weasnerb/angular-phonecat-migration/tree/siblingRoutesSinkRoute

Neither strategy works! What am I doing wrong?

[weasnerb]

I also want to note that I subscribed to the angular router in the app component and output everything to the console. There was nothing logged. I believe that angular just isn't aware of the route changes in this hybrid application?

[weasnerb]

Looks like I found the one line of code that allows the routers to work together: setUpLocationSync(upgrade);

I am still not getting the angular component to show up using a custom UrlHandlingStrategy