-
Notifications
You must be signed in to change notification settings - Fork 6.8k
feat(schematics): compatibility with Angular CLI 6.2.0 #13078
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(schematics): compatibility with Angular CLI 6.2.0 #13078
Conversation
* Upgrades the devkit dependencies to the latest versions. * Adds support for the newly introduced and published `project.targets` instead of `project.architect` (see: angular/angular-cli@3071608) * Compatibility behavior for a published but non-announced breaking change within the schematic context (see: https://github.com/angular/angular-cli/commit/9720077a4b5ae628ddfaf5f1a26bac3b04bdf637#diff-e73df838d6700d187eff76a50c7e1c53R233`) * Supports the new `project.targets` schema within the update schematics (in order to properly determine `tsconfig` files) Fixes angular#11438
if (project.architect && | ||
project.architect[targetName] && | ||
project.architect[targetName].options && | ||
project.architect[targetName].options.tsConfig) { |
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.
I know that we could extract this into a more generic function in order to reduce duplication, but I prefer being explicit here.
34cf0ae
to
ddd9927
Compare
* Due to the fact that the @angular-devkit/schematics now handles Bazel better, the template files will be resolved through NodeJS. This means that the template files need to be referenced in the @//:node_modules label.
ddd9927
to
1b76f15
Compare
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.
LGTM
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
project.targets
instead ofproject.architect
(see: angular/angular-cli@3071608)project.targets
schema within the update schematics (in order to properly determinetsconfig
files)Fixes #11438