honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/compiler/test/selector/BUILD.bazel

34 lines
805 B
Python
Raw Normal View History

build: ts_web_test & ts_web_test_suite deprecated in favor of karma_web_test & karma_web_test_suite (#33802) This is a breaking change in nodejs rules 0.40.0 as part of the API review & cleanup for the 1.0 release. Their APIs are identical as ts_web_test was just karma_web_test without the config_file attribute. PR Close #33802
2019-11-13 12:08:38 -05:00
load("//tools:defaults.bzl", "jasmine_node_test", "karma_web_test_suite", "ts_library")
test(ivy): update //packages/compiler tests for Ivy (#27301) Most of the specs in these tests are not relevant to Ivy: //packages/compiler/test:test //packages/compiler/test:test_web_chromium-local However, a few test pieces of the compiler infrastructure that are used in Ivy, and new BUILD.bazel files are created to separate them from the above disabled targets: //packages/compiler/test/css_parser:css_parser //packages/compiler/test/css_parser:css_parser_web //packages/compiler/test/expression_parser:expression_parser //packages/compiler/test/expression_parser:expression_parser_web //packages/compiler/test/ml_parser:ml_parser //packages/compiler/test/ml_parser:ml_parser_web //packages/compiler/test/selector:selector //packages/compiler/test/selector:selector_web PR Close #27301
2018-11-27 15:32:14 -05:00
ts_library(
name = "selector_lib",
testonly = True,
srcs = glob(["**/*.ts"]),
deps = [
"//packages:types",
refactor: Move `dom_adapter.ts` to `@angular/common` (#32154) This work is needed in preparation for turning tokens into tree-shakable injectables. PR Close #32154
2019-08-22 22:16:25 -04:00
"//packages/common",
build: fix type-check errors introduced during rules_ts 0.21 (#27586) PR Close #27586
2018-12-10 17:36:45 -05:00
"//packages/compiler",
test(ivy): update //packages/compiler tests for Ivy (#27301) Most of the specs in these tests are not relevant to Ivy: //packages/compiler/test:test //packages/compiler/test:test_web_chromium-local However, a few test pieces of the compiler infrastructure that are used in Ivy, and new BUILD.bazel files are created to separate them from the above disabled targets: //packages/compiler/test/css_parser:css_parser //packages/compiler/test/css_parser:css_parser_web //packages/compiler/test/expression_parser:expression_parser //packages/compiler/test/expression_parser:expression_parser_web //packages/compiler/test/ml_parser:ml_parser //packages/compiler/test/ml_parser:ml_parser_web //packages/compiler/test/selector:selector //packages/compiler/test/selector:selector_web PR Close #27301
2018-11-27 15:32:14 -05:00
"//packages/compiler/testing",
"//packages/core/testing",
build: fix type-check errors introduced during rules_ts 0.21 (#27586) PR Close #27586
2018-12-10 17:36:45 -05:00
"//packages/platform-browser",
"//packages/platform-browser/testing",
test(ivy): update //packages/compiler tests for Ivy (#27301) Most of the specs in these tests are not relevant to Ivy: //packages/compiler/test:test //packages/compiler/test:test_web_chromium-local However, a few test pieces of the compiler infrastructure that are used in Ivy, and new BUILD.bazel files are created to separate them from the above disabled targets: //packages/compiler/test/css_parser:css_parser //packages/compiler/test/css_parser:css_parser_web //packages/compiler/test/expression_parser:expression_parser //packages/compiler/test/expression_parser:expression_parser_web //packages/compiler/test/ml_parser:ml_parser //packages/compiler/test/ml_parser:ml_parser_web //packages/compiler/test/selector:selector //packages/compiler/test/selector:selector_web PR Close #27301
2018-11-27 15:32:14 -05:00
],
)
jasmine_node_test(
name = "selector",
refactor: handle breaking changes in rules_nodejs 1.0.0 (#34736) The major one that affects the angular repo is the removal of the bootstrap attribute in nodejs_binary, nodejs_test and jasmine_node_test in favor of using templated_args --node_options=--require=/path/to/script. The side-effect of this is that the bootstrap script does not get the require.resolve patches with explicitly loading the targets _loader.js file. PR Close #34736
2019-12-28 21:14:36 -05:00
templated_args = ["--node_options=--require=$(rlocation $(location //tools/testing:node_es5))"],
test(ivy): update //packages/compiler tests for Ivy (#27301) Most of the specs in these tests are not relevant to Ivy: //packages/compiler/test:test //packages/compiler/test:test_web_chromium-local However, a few test pieces of the compiler infrastructure that are used in Ivy, and new BUILD.bazel files are created to separate them from the above disabled targets: //packages/compiler/test/css_parser:css_parser //packages/compiler/test/css_parser:css_parser_web //packages/compiler/test/expression_parser:expression_parser //packages/compiler/test/expression_parser:expression_parser_web //packages/compiler/test/ml_parser:ml_parser //packages/compiler/test/ml_parser:ml_parser_web //packages/compiler/test/selector:selector //packages/compiler/test/selector:selector_web PR Close #27301
2018-11-27 15:32:14 -05:00
deps = [
":selector_lib",
Revert "build: derive ts_library dep from jasmine_node_test boostrap label if it ends in `_es5` (#34589)" (#34730) This reverts commit 79a0d007b4e892dd988a8ef697e6d3436ea8391c. PR Close #34730
2020-01-10 16:39:37 -05:00
"//tools/testing:node",
refactor: handle breaking changes in rules_nodejs 1.0.0 (#34736) The major one that affects the angular repo is the removal of the bootstrap attribute in nodejs_binary, nodejs_test and jasmine_node_test in favor of using templated_args --node_options=--require=/path/to/script. The side-effect of this is that the bootstrap script does not get the require.resolve patches with explicitly loading the targets _loader.js file. PR Close #34736
2019-12-28 21:14:36 -05:00
"//tools/testing:node_es5",
test(ivy): update //packages/compiler tests for Ivy (#27301) Most of the specs in these tests are not relevant to Ivy: //packages/compiler/test:test //packages/compiler/test:test_web_chromium-local However, a few test pieces of the compiler infrastructure that are used in Ivy, and new BUILD.bazel files are created to separate them from the above disabled targets: //packages/compiler/test/css_parser:css_parser //packages/compiler/test/css_parser:css_parser_web //packages/compiler/test/expression_parser:expression_parser //packages/compiler/test/expression_parser:expression_parser_web //packages/compiler/test/ml_parser:ml_parser //packages/compiler/test/ml_parser:ml_parser_web //packages/compiler/test/selector:selector //packages/compiler/test/selector:selector_web PR Close #27301
2018-11-27 15:32:14 -05:00
],
)
build: ts_web_test & ts_web_test_suite deprecated in favor of karma_web_test & karma_web_test_suite (#33802) This is a breaking change in nodejs rules 0.40.0 as part of the API review & cleanup for the 1.0 release. Their APIs are identical as ts_web_test was just karma_web_test without the config_file attribute. PR Close #33802
2019-11-13 12:08:38 -05:00
karma_web_test_suite(
test(ivy): update //packages/compiler tests for Ivy (#27301) Most of the specs in these tests are not relevant to Ivy: //packages/compiler/test:test //packages/compiler/test:test_web_chromium-local However, a few test pieces of the compiler infrastructure that are used in Ivy, and new BUILD.bazel files are created to separate them from the above disabled targets: //packages/compiler/test/css_parser:css_parser //packages/compiler/test/css_parser:css_parser_web //packages/compiler/test/expression_parser:expression_parser //packages/compiler/test/expression_parser:expression_parser_web //packages/compiler/test/ml_parser:ml_parser //packages/compiler/test/ml_parser:ml_parser_web //packages/compiler/test/selector:selector //packages/compiler/test/selector:selector_web PR Close #27301
2018-11-27 15:32:14 -05:00
name = "selector_web",
deps = [
":selector_lib",
],
)