Repository navigation
Name outlets doesn't work with lazy loaded modules. #17343
Description
I am submitting a [x] bug report
Current behavior
with lazy loaded modules I can not visit its child routes that uses named outlets.
For example
localhost:3000/heroes/(abc:list) doesn't work where heroes module is lazy loaded.
Expected behavior
I should be able to visit localhost:3000/heroes/(abc:list)
Minimal reproduction of the problem with instructions
Go to https://plnkr.co/edit/NNXAoZItM00RIIxzemts?p=preview and download the sample app into a zip file then run it by npm install and npm start.
What is the motivation / use case for changing the behavior?
To lazy load module with name outlets.
Please tell us about your environment:
Windows 10, visual studio code, chrome
- Angular version:
4.0 - Browser:
Chrome, Firefox
- Language: [all | TypeScript X.X | ES6/7 | ES5]
TypeScript
Activity
Simon-Briggs commentedon Jun 9, 2017
Related to #10981 ?
jasonaden commentedon Jul 18, 2017
Duplicate of #10981
Jonathan002 commentedon Jul 20, 2019
@markqian Hi Markqian, I've created a workaround solution that is intended to help with named outlets and lazy modules. Please have a look and hope this helps.
Repo: https://github.com/Jonathan002/route-master-example
angular-automatic-lock-bot commentedon Sep 15, 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.