From c0627d1a493f974edbc6281bd5acd1d50d3eab14 Mon Sep 17 00:00:00 2001 From: Guilherme Siquinelli Date: Fri, 16 Oct 2020 18:32:10 -0300 Subject: [PATCH] fix(angular): angular library was not checking to see if an import path exists (#3888) loading child paths into an angular library was not checking to see if an import path exists, so it generated the wrong path. the unit tests of the angular package are working. I generated a local release with verdaccio after the correction and generated the right children path. --- .../angular/src/schematics/library/lib/add-load-children.ts | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/angular/src/schematics/library/lib/add-load-children.ts b/packages/angular/src/schematics/library/lib/add-load-children.ts index ddaefe64e4214..6b1a6cb7d98f3 100644 --- a/packages/angular/src/schematics/library/lib/add-load-children.ts +++ b/packages/angular/src/schematics/library/lib/add-load-children.ts @@ -33,8 +33,8 @@ export function addLoadChildren(options: NormalizedSchema): Rule { sourceFile, `{path: '${toFileName( options.fileName - )}', loadChildren: () => import('@${npmScope}/${ - options.projectDirectory + )}', loadChildren: () => import('${ + options.importPath }').then(module => module.${options.moduleName})}` ), ]);