Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
angular/packages/compiler/test/expression_parser/BUILD.bazel

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

28 lines
611 B
Text
Raw Normal View History

refactor(compiler): remove zone-based testing utilities Having zone.js here already wasn't necessary.
2026-02-06 00:05:09 +00:00
load("//tools:defaults.bzl", "ng_web_test_suite", "ts_project", "zoneless_jasmine_test")
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 20:32:14 +00:00
build: migrate `packages/compiler` to `ts_project` (#61566) Migrates `packages/compiler` to `ts_project`. PR Close #61566
2025-05-20 11:47:20 +00:00
ts_project(
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 20:32:14 +00:00
name = "expression_parser_lib",
testonly = True,
srcs = glob(["**/*.ts"]),
build: remove all usages of the interop_deps attr for ts_project and ng_project (#62732) Remove all of the usages of interop_deps as attributes in the repo PR Close #62732
2025-07-21 15:29:15 +00:00
deps = [
build: remove ts_project_interop infrastructure (#62908) Remove the interop macros and final usages PR Close #62908
2025-07-30 17:43:25 +00:00
"//packages/compiler",
"//packages/compiler/test/expression_parser/utils",
"//packages/platform-browser/testing",
"//packages/private/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 20:32:14 +00:00
],
)
refactor(compiler): remove zone-based testing utilities Having zone.js here already wasn't necessary.
2026-02-06 00:05:09 +00:00
zoneless_jasmine_test(
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 20:32:14 +00:00
name = "expression_parser",
build: migrate to using new jasmine_test (#62086) Use the new jasmine_test based on rules_js instead of jasmine_node_test from rules_nodejs PR Close #62086
2025-06-16 18:07:36 +00:00
data = [
build: remove ts_project_interop infrastructure (#62908) Remove the interop macros and final usages PR Close #62908
2025-07-30 17:43:25 +00:00
":expression_parser_lib",
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 20:32:14 +00:00
],
)
build: migrate to use web test runner rules (#62292) Migrate karma tests throughout the repo to use the new web test runner based rule instead PR Close #62292
2025-06-26 12:50:03 +00:00
ng_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 20:32:14 +00:00
name = "expression_parser_web",
deps = [
build: remove ts_project_interop infrastructure (#62908) Remove the interop macros and final usages PR Close #62908
2025-07-30 17:43:25 +00:00
":expression_parser_lib",
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 20:32:14 +00:00
],
)
Reference in a new issue Copy permalink