You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
Current behavior
I do have a lazy loaded module which loads by default LazyLoadedComponent when I go to /lazy. So far, it's OK.
Is this a bug with the router ? Is it just me missing out something here?
You can check out this Plunkr to make your own tests.
Minimal reproduction of the problem with instructions Plunkr :
Click on "Demo (click to lazy load the module)"
Once the module is loaded, click on "Load an auxiliary route"
The non auxiliary component is well displayed, the auxiliary component is not displayed
Please tell us about your environment:
Ubuntu 16.10
VSC
Yarn
(But as this is also happening on Plunkr, not sure it's relevant).
Angular version: 2.0.X
v2.4.1 (the one used on Plunkr)
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Activity
DzmitryShylovich commentedon Jan 6, 2017
Duplicate of #10981
maxime1992 commentedon Jan 6, 2017
It seems that it isn't even a problem with lazy loaded modules containing aux routes.
Using
loadChildren : () => ModuleNamealso result in error.vicb commentedon Jan 6, 2017
Closing as duplicate.
topaxi commentedon Jun 18, 2018
#10981 has been fixed but this case is still not working, I'd guess because of the empty path in the parent route.
luckylooke commentedon Oct 12, 2018
@topaxi I can confirm that it is empty path related, I have posted examples here #10981 (comment)
angular-automatic-lock-bot commentedon Sep 14, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.