Router, lazy-loaded module: loading children into named outlet throws NoMatch error #11208

Closed
mrkosima opened this Issue Aug 31, 2016 · 9 comments

Comments

Projects
None yet
9 participants
@mrkosima

mrkosima commented Aug 31, 2016

I'm submitting a [x] bug report

Current behavior
Error when navigating to lazy loaded route with lazy loaded children into named outlet:
Error: Uncaught (in promise): Error: Cannot match any routes: ...

Expected/desired behavior
Navigating to lazy loaded route with lazy loaded children in named outlet without errors

Reproduction of the problem
https://embed.plnkr.co/HgZjNRdrYSvnmdzE01zO/
Click Primary->Level1 - works ok.
Click OutletA->Level2 - got error.
Click OutletB->Level1 - got error

Notes
Additional experimental cases with modules and routes you can find in repo:
https://github.com/mrkosima/angular-rc5-router-lazy-in-lazy

Please tell us about your environment:

  • Angular version: 2.0.0-rc.5/2.0.0-rc.6
  • Router version: 3.0.0-rc.1/3.0.0-rc.2
  • Browser: [Chrome 52]
  • Language: [TypeScript 1.8.10]
@mrkosima

This comment has been minimized.

Show comment
Hide comment
@mrkosima

mrkosima Sep 1, 2016

reproduced with angular:2.0.0-rc.6 and router:3.0.0-rc.2

mrkosima commented Sep 1, 2016

reproduced with angular:2.0.0-rc.6 and router:3.0.0-rc.2

@vijayantkatyal

This comment has been minimized.

Show comment
Hide comment
@vijayantkatyal

vijayantkatyal Sep 8, 2016

i'm having the same issue.

i'm having the same issue.

@michaelchiche

This comment has been minimized.

Show comment
Hide comment
@michaelchiche

michaelchiche Sep 12, 2016

Contributor

we have the same problem in our app :(

Contributor

michaelchiche commented Sep 12, 2016

we have the same problem in our app :(

@ivanStraltsou

This comment has been minimized.

Show comment
Hide comment

same issue

@srenaudon

This comment has been minimized.

Show comment
Hide comment
@srenaudon

srenaudon Sep 22, 2016

Same kind of issue ...
Routes defined in named outlet in a lazy-loaded module are not matched .

Same kind of issue ...
Routes defined in named outlet in a lazy-loaded module are not matched .

@PraveenPeri

This comment has been minimized.

Show comment
Hide comment
@PraveenPeri

PraveenPeri Sep 22, 2016

Same problem here! Hoping for a fix/workaround asap.

Same problem here! Hoping for a fix/workaround asap.

@molcik

This comment has been minimized.

Show comment
Hide comment
@molcik

molcik Nov 12, 2016

Is it going to work some day? Or "Componentless route cannot have a named outlet set" and, it should be feature request?

molcik commented Nov 12, 2016

Is it going to work some day? Or "Componentless route cannot have a named outlet set" and, it should be feature request?

@mrkosima

This comment has been minimized.

Show comment
Hide comment
@mrkosima

mrkosima Nov 14, 2016

@molcik, good question
tnx for opening #12842

@molcik, good question
tnx for opening #12842

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment