-
Notifications
You must be signed in to change notification settings - Fork 155
Conversation
@jschwarty PR #29 contains the updates for module resolutions. |
56abe48
to
8fb84b5
Compare
} | ||
|
||
let modulePath; | ||
if (options.module) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This check is redundant (see line 33)
Once that's removed modulePath
can be a const instead of being let
and set on line 42.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something like this?
if (!options.module) {
return host;
}
const modulePath = options.module;
if (!host.exists(options.module)) {
throw new Error(`Module specified (${options.module}) does not exist.`);
}
package-lock.json
Outdated
@@ -12,10 +12,14 @@ | |||
"@ngtools/logger": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There should be no changes to package-lock.json
in this PR either
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a bad merge. just reset it.
8fb84b5
to
021a02e
Compare
template, | ||
url, | ||
} from '@angular-devkit/schematics'; | ||
import * as stringUtils from '../strings'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please merge all import groups together (this is different than the CLI repo).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So just no empty line here between import
lines, correct?
021a02e
to
2a089e2
Compare
Have a
TODO
in there for the module name option as per discussion with @Brocco. Also, thepackage-lock.json
file is in here. Not sure what the plan is to handle that as it changes from dev to dev. Let me know if I need to do anything on that.