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
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
4.0
Chrome, Firefox
TypeScript