From feba96d62e31b7e6f231eef94732a8a7011b8f8f Mon Sep 17 00:00:00 2001 From: Panayot Cankov Date: Mon, 11 Dec 2017 12:49:09 +0200 Subject: [PATCH] refactor: loadChildren to work with ~/path and ./path both relative to app/ It turns out the ./path for loadChildren have never worked as relative to the routes module, and was always expected to be relative to app/ in non-webpack builds. Modifying the lazy loaded ninjas to feature both ./ and ~/ paths relative to the app. --- demo/AngularApp/app/ninjas/ninjas.component.ts | 4 ++-- demo/AngularApp/app/ninjas/ninjas.routes.ts | 6 +++++- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/demo/AngularApp/app/ninjas/ninjas.component.ts b/demo/AngularApp/app/ninjas/ninjas.component.ts index 1e46b460..508a54dd 100644 --- a/demo/AngularApp/app/ninjas/ninjas.component.ts +++ b/demo/AngularApp/app/ninjas/ninjas.component.ts @@ -6,13 +6,13 @@ import { Component } from "@angular/core"; - + + [nsRouterLink]="['details' + (index % 2 + 1) , ninja.name]"> diff --git a/demo/AngularApp/app/ninjas/ninjas.routes.ts b/demo/AngularApp/app/ninjas/ninjas.routes.ts index 6efec2d7..820d6e77 100644 --- a/demo/AngularApp/app/ninjas/ninjas.routes.ts +++ b/demo/AngularApp/app/ninjas/ninjas.routes.ts @@ -6,7 +6,11 @@ export const routes = [ component: NinjasComponent }, { - path: "details", + path: "details1", + loadChildren: "./ninjas/details/ninja.module#NinjaModule", + }, + { + path: "details2", loadChildren: "~/ninjas/details/ninja.module#NinjaModule", }, ];