honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/core/schematics/utils/BUILD.bazel

18 lines
492 B
Python
Raw Normal View History

feat(core): update schematic to migrate to explicit query timing (#28983) Introduces an update schematic for the "@angular/core" package that automatically migrates pre-V8 "ViewChild" and "ContentChild" queries to the new explicit timing syntax. This is not required yet, but with Ivy, queries will be "dynamic" by default. Therefore specifying an explicit query timing ensures that developers can smoothly migrate to Ivy (once it's the default). Read more about the explicit timing API here: https://github.com/angular/angular/pull/28810 PR Close #28983
2019-02-27 14:30:38 -05:00
load("//tools:defaults.bzl", "ts_library")
ts_library(
name = "utils",
refactor(core): add tslint rule entry-point for static-query migration (#29258) In order to be able to use the static-query migration logic within Google, we need to provide a TSLint rule entry-point that wires up the schematic logic and provides reporting and automatic fixes. PR Close #29258
2019-03-13 11:29:25 -04:00
srcs = glob(["**/*.ts"]),
feat(core): update schematic to migrate to explicit query timing (#28983) Introduces an update schematic for the "@angular/core" package that automatically migrates pre-V8 "ViewChild" and "ContentChild" queries to the new explicit timing syntax. This is not required yet, but with Ivy, queries will be "dynamic" by default. Therefore specifying an explicit query timing ensures that developers can smoothly migrate to Ivy (once it's the default). Read more about the explicit timing API here: https://github.com/angular/angular/pull/28810 PR Close #28983
2019-02-27 14:30:38 -05:00
tsconfig = "//packages/core/schematics:tsconfig.json",
visibility = ["//packages/core/schematics:__subpackages__"],
refactor(core): static-query schematic should not run multiple times (#29133) With 6215799, we introduced a schematic for the new static-query timing. Currently when someone runs the update schematic manually within his CLI project (the schematic does not run automatically yet), he might have noticed that the migration is executed for the same `tsconfig` file multiple times. This can happen because the `getProjectTsConfigPaths` function can incorrectly return the same tsconfig multiple times. The paths are not properly deduped as we don't normalize the determined project tsconfig paths PR Close #29133
2019-03-09 10:58:26 -05:00
deps = [
refactor(core): static-query schematic should check templates (#29713) Queries can technically be also accessed within component templates e.g. ```html <my-comp [binding]="myQuery"></my-comp> ``` In that case the query with the property "myQuery" is accessed statically and needs to be marked with `static: true`. There are other edge cases that need to be handled as the template property read doesn't necessarily resolve to the actual query property. For example: ```html <foo #myQuery></foo> <my-comp [binding]="myQuery"></my-comp> ``` In this scenario the binding doesn't refer to the actual query because the template reference variable takes precedence. The query doesn't need to be marked with "static: true" this time. This commit ensures that the `static-query` migration schematic now handles this cases properly. Also template property reads that access queries from within a `<ng-template>` are ignored as these can't access the query before the view has been initialized. Resolves FW-1216 PR Close #29713
2019-04-08 10:16:56 -04:00
"//packages/compiler",
refactor(core): static-query schematic should not run multiple times (#29133) With 6215799, we introduced a schematic for the new static-query timing. Currently when someone runs the update schematic manually within his CLI project (the schematic does not run automatically yet), he might have noticed that the migration is executed for the same `tsconfig` file multiple times. This can happen because the `getProjectTsConfigPaths` function can incorrectly return the same tsconfig multiple times. The paths are not properly deduped as we don't normalize the determined project tsconfig paths PR Close #29133
2019-03-09 10:58:26 -05:00
"@npm//@angular-devkit/core",
"@npm//@angular-devkit/schematics",
build: update rules_nodejs and clean up bazel warnings (#30370) Preserve compatibility with rollup_bundle rule. Add missing npm dependencies, which are now enforced by the strict_deps plugin in tsc_wrapped PR Close #30370
2019-05-09 17:51:51 -04:00
"@npm//@schematics/angular",
build: update to rules_nodejs 0.32.2 (#31325) Brings in ts_library fixes required to get angular/angular building after 0.32.0: typescript: exclude typescript lib declarations in node_module_library transitive_declarations typescript: remove override of @bazel/tsetse (+1 squashed commit) @npm//node_modules/foobar:foobar.js labels changed to @npm//:node_modules/foobar/foobar.js with fix for bazelbuild/rules_nodejs#802 also updates to rules_rass commit compatible with rules_nodejs 0.32.0 PR Close #31325
2019-06-19 00:26:53 -04:00
"@npm//@types/inquirer",
build: update rules_nodejs and clean up bazel warnings (#30370) Preserve compatibility with rollup_bundle rule. Add missing npm dependencies, which are now enforced by the strict_deps plugin in tsc_wrapped PR Close #30370
2019-05-09 17:51:51 -04:00
"@npm//@types/node",
"@npm//typescript",
refactor(core): static-query schematic should not run multiple times (#29133) With 6215799, we introduced a schematic for the new static-query timing. Currently when someone runs the update schematic manually within his CLI project (the schematic does not run automatically yet), he might have noticed that the migration is executed for the same `tsconfig` file multiple times. This can happen because the `getProjectTsConfigPaths` function can incorrectly return the same tsconfig multiple times. The paths are not properly deduped as we don't normalize the determined project tsconfig paths PR Close #29133
2019-03-09 10:58:26 -05:00
],
feat(core): update schematic to migrate to explicit query timing (#28983) Introduces an update schematic for the "@angular/core" package that automatically migrates pre-V8 "ViewChild" and "ContentChild" queries to the new explicit timing syntax. This is not required yet, but with Ivy, queries will be "dynamic" by default. Therefore specifying an explicit query timing ensures that developers can smoothly migrate to Ivy (once it's the default). Read more about the explicit timing API here: https://github.com/angular/angular/pull/28810 PR Close #28983
2019-02-27 14:30:38 -05:00
)