Angular 7 multiple router-outlets and lazyloading
I have an app with the following structure
app/
├── app.component.html
├── app.component.scss
├── app.component.ts
├── app.module.ts
├── core/
│ ├── core-routing.module.ts
│ ├── core.module.spec.ts
│ ├── core.module.ts
│ ├── header/
│ ├── layout/
│ ├── services/
│ └── header/
├── someModule1/
├── someModule2/
The AppModule
which occupies the root of the folder is kept as bare as possible. It’s role is simply to bootstrap the Angular application, and provide the root-level router-outlet
.
Everything runs through the CoreModule
. The CoreModule
routes are the following (forRoot()):
const routes: Routes = [
{
path: 'app',
component: LayoutComponent,
},
{
path: 'somePath',
loadChildren: '../someModule1/someModule1.module#SomeModule1'
},
{
path: '**', component: NotFoundComponent
}
];
It allows me to instantiate my LayoutComponent
which has the content displayed through the main router-outlet
and a secondary named outlet for other components to display.
<header-component></header-component>
<mat-drawer-container>
<mat-drawer #drawer>
<router-outlet name="sidenav"></router-outlet>
</mat-drawer>
<div class="sidenav-content">
<router-outlet></router-outlet>
</div>
</mat-drawer-container>
I did try everything I could to display separate content in sidenav and main-content area without any success.
I expect <a [routerLink]="['somepath', { outlets: { sidenav: ['foo'] } }]">Outlet Nav</a>
to display somepath
in <router-outlet></router-outlet>
and foo
in <router-outlet name="foo"></router-outlet>
What am I doing wrong ? I've read that it could be related with lazyloading modules
angular router angular7
add a comment |
I have an app with the following structure
app/
├── app.component.html
├── app.component.scss
├── app.component.ts
├── app.module.ts
├── core/
│ ├── core-routing.module.ts
│ ├── core.module.spec.ts
│ ├── core.module.ts
│ ├── header/
│ ├── layout/
│ ├── services/
│ └── header/
├── someModule1/
├── someModule2/
The AppModule
which occupies the root of the folder is kept as bare as possible. It’s role is simply to bootstrap the Angular application, and provide the root-level router-outlet
.
Everything runs through the CoreModule
. The CoreModule
routes are the following (forRoot()):
const routes: Routes = [
{
path: 'app',
component: LayoutComponent,
},
{
path: 'somePath',
loadChildren: '../someModule1/someModule1.module#SomeModule1'
},
{
path: '**', component: NotFoundComponent
}
];
It allows me to instantiate my LayoutComponent
which has the content displayed through the main router-outlet
and a secondary named outlet for other components to display.
<header-component></header-component>
<mat-drawer-container>
<mat-drawer #drawer>
<router-outlet name="sidenav"></router-outlet>
</mat-drawer>
<div class="sidenav-content">
<router-outlet></router-outlet>
</div>
</mat-drawer-container>
I did try everything I could to display separate content in sidenav and main-content area without any success.
I expect <a [routerLink]="['somepath', { outlets: { sidenav: ['foo'] } }]">Outlet Nav</a>
to display somepath
in <router-outlet></router-outlet>
and foo
in <router-outlet name="foo"></router-outlet>
What am I doing wrong ? I've read that it could be related with lazyloading modules
angular router angular7
add a comment |
I have an app with the following structure
app/
├── app.component.html
├── app.component.scss
├── app.component.ts
├── app.module.ts
├── core/
│ ├── core-routing.module.ts
│ ├── core.module.spec.ts
│ ├── core.module.ts
│ ├── header/
│ ├── layout/
│ ├── services/
│ └── header/
├── someModule1/
├── someModule2/
The AppModule
which occupies the root of the folder is kept as bare as possible. It’s role is simply to bootstrap the Angular application, and provide the root-level router-outlet
.
Everything runs through the CoreModule
. The CoreModule
routes are the following (forRoot()):
const routes: Routes = [
{
path: 'app',
component: LayoutComponent,
},
{
path: 'somePath',
loadChildren: '../someModule1/someModule1.module#SomeModule1'
},
{
path: '**', component: NotFoundComponent
}
];
It allows me to instantiate my LayoutComponent
which has the content displayed through the main router-outlet
and a secondary named outlet for other components to display.
<header-component></header-component>
<mat-drawer-container>
<mat-drawer #drawer>
<router-outlet name="sidenav"></router-outlet>
</mat-drawer>
<div class="sidenav-content">
<router-outlet></router-outlet>
</div>
</mat-drawer-container>
I did try everything I could to display separate content in sidenav and main-content area without any success.
I expect <a [routerLink]="['somepath', { outlets: { sidenav: ['foo'] } }]">Outlet Nav</a>
to display somepath
in <router-outlet></router-outlet>
and foo
in <router-outlet name="foo"></router-outlet>
What am I doing wrong ? I've read that it could be related with lazyloading modules
angular router angular7
I have an app with the following structure
app/
├── app.component.html
├── app.component.scss
├── app.component.ts
├── app.module.ts
├── core/
│ ├── core-routing.module.ts
│ ├── core.module.spec.ts
│ ├── core.module.ts
│ ├── header/
│ ├── layout/
│ ├── services/
│ └── header/
├── someModule1/
├── someModule2/
The AppModule
which occupies the root of the folder is kept as bare as possible. It’s role is simply to bootstrap the Angular application, and provide the root-level router-outlet
.
Everything runs through the CoreModule
. The CoreModule
routes are the following (forRoot()):
const routes: Routes = [
{
path: 'app',
component: LayoutComponent,
},
{
path: 'somePath',
loadChildren: '../someModule1/someModule1.module#SomeModule1'
},
{
path: '**', component: NotFoundComponent
}
];
It allows me to instantiate my LayoutComponent
which has the content displayed through the main router-outlet
and a secondary named outlet for other components to display.
<header-component></header-component>
<mat-drawer-container>
<mat-drawer #drawer>
<router-outlet name="sidenav"></router-outlet>
</mat-drawer>
<div class="sidenav-content">
<router-outlet></router-outlet>
</div>
</mat-drawer-container>
I did try everything I could to display separate content in sidenav and main-content area without any success.
I expect <a [routerLink]="['somepath', { outlets: { sidenav: ['foo'] } }]">Outlet Nav</a>
to display somepath
in <router-outlet></router-outlet>
and foo
in <router-outlet name="foo"></router-outlet>
What am I doing wrong ? I've read that it could be related with lazyloading modules
angular router angular7
angular router angular7
edited Nov 28 '18 at 18:58
Goncalo Peres
1,4591519
1,4591519
asked Nov 14 '18 at 10:36
ThomasThomas
63
63
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53298188%2fangular-7-multiple-router-outlets-and-lazyloading%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53298188%2fangular-7-multiple-router-outlets-and-lazyloading%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown