angular-cn/packages/core/test/render3/ivy/BUILD.bazel

load("//tools:defaults.bzl", "jasmine_node_test", "ts_library")

package(default_visibility = ["//visibility:public"])

ts_library(
    name = "ivy_lib",
    testonly = True,
    srcs = glob(["**/*.ts"]),
    deps = [
        "//packages:types",
        "//packages/core",
        "//packages/core/src/di/interface",
    ],
)

jasmine_node_test(
    name = "ivy",
    bootstrap = [
        "angular/packages/core/test/render3/load_domino",
    ],
    tags = [
        "ivy-only",
    ],
    deps = [
        ":ivy_lib",
        "//packages/core/test/render3:domino",
    ],
)
style: enforce buildifier lint on CI (#28186) PR Close #28186 2019-01-16 10:19:01 +01:00			`load("//tools:defaults.bzl", "jasmine_node_test", "ts_library")`
feat(ivy): first steps towards JIT compilation (#23833) This commit adds a mechanism by which the @angular/core annotations for @Component, @Injectable, and @NgModule become decorators which, when executed at runtime, trigger just-in-time compilation of their associated types. The activation of these decorators is configured by the ivy_switch mechanism, ensuring that the Ivy JIT engine does not get included in Angular bundles unless specifically requested. PR Close #23833 2018-05-09 08:35:25 -07:00
style: enforce buildifier lint on CI (#28186) PR Close #28186 2019-01-16 10:19:01 +01:00			`package(default_visibility = ["//visibility:public"])`
feat(ivy): first steps towards JIT compilation (#23833) This commit adds a mechanism by which the @angular/core annotations for @Component, @Injectable, and @NgModule become decorators which, when executed at runtime, trigger just-in-time compilation of their associated types. The activation of these decorators is configured by the ivy_switch mechanism, ensuring that the Ivy JIT engine does not get included in Angular bundles unless specifically requested. PR Close #23833 2018-05-09 08:35:25 -07:00
			`ts_library(`
			`name = "ivy_lib",`
test(ivy): mark failing test targets with fixme-ivy-jit and fixme-ivy-local tags (#26471) We are close enough to blacklist a few test targets, rather than whitelist targets to run... Because bazel rules can be composed of other rules that don't inherit tags automatically, I had to explicitly mark all of our ts_library and ng_module targes with "ivy-local" and "ivy-jit" tags so that we can create a query that excludes all fixme- tagged targets even if those targets are composed of other targets that don't inherit this tag. This is the updated overview of ivy related bazel tags: - ivy-only: target that builds or runs only under ivy - fixme-ivy-jit: target that doesn't yet build or run under ivy with --compile=jit - fixme-ivy-local: target that doesn't yet build or run under ivy with --compile=local - no-ivy-jit: target that is not intended to build or run under ivy with --compile=jit - no-ivy-local: target that is not intended to build or run under ivy with --compile=local PR Close #26471 2018-10-15 23:24:22 -07:00			`testonly = True,`
feat(ivy): first steps towards JIT compilation (#23833) This commit adds a mechanism by which the @angular/core annotations for @Component, @Injectable, and @NgModule become decorators which, when executed at runtime, trigger just-in-time compilation of their associated types. The activation of these decorators is configured by the ivy_switch mechanism, ensuring that the Ivy JIT engine does not get included in Angular bundles unless specifically requested. PR Close #23833 2018-05-09 08:35:25 -07:00			`srcs = glob(["*/.ts"]),`
			`deps = [`
			`"//packages:types",`
			`"//packages/core",`
build: extract interface and util sub compilation from core (#28028) PR Close #28028 2019-01-09 13:49:16 -08:00			`"//packages/core/src/di/interface",`
feat(ivy): first steps towards JIT compilation (#23833) This commit adds a mechanism by which the @angular/core annotations for @Component, @Injectable, and @NgModule become decorators which, when executed at runtime, trigger just-in-time compilation of their associated types. The activation of these decorators is configured by the ivy_switch mechanism, ensuring that the Ivy JIT engine does not get included in Angular bundles unless specifically requested. PR Close #23833 2018-05-09 08:35:25 -07:00			`],`
			`)`

			`jasmine_node_test(`
			`name = "ivy",`
			`bootstrap = [`
			`"angular/packages/core/test/render3/load_domino",`
			`],`
fix(ivy): compute transitive scopes from NgModuleDef only (#24334) Previously, the transitive scopes of an NgModuleDef were computed during execution of the @NgModule decorator. This meant that JIT- compiled modules could only import other JIT-compiled modules, as the import mechanism relied on the calculation of transitive scopes to already have happened for the imported module. This change moves computation of transitive scopes to a function `transitiveScopesFor` (and makes it lazy). This opens the door for AOT -> JIT or JIT -> AOT imports, as transitive scopes for AOT modules can be calculated when needed by JIT, and AOT modules can also write expressions that call `transitiveScopesFor` when importing a JIT-compiled module. PR Close #24334 2018-06-06 11:23:38 -07:00			`tags = [`
test(ivy): fix or disable failing ivy tests (#26735) These tests were previously not running on CI so they have always been broken, or got broken just recently :-(. test(ivy): mark failing test targets with fixme-ivy-jit and fixme-ivy-local tags PR Close #26735 2018-10-25 20:47:28 -07:00			`"ivy-only",`
fix(ivy): compute transitive scopes from NgModuleDef only (#24334) Previously, the transitive scopes of an NgModuleDef were computed during execution of the @NgModule decorator. This meant that JIT- compiled modules could only import other JIT-compiled modules, as the import mechanism relied on the calculation of transitive scopes to already have happened for the imported module. This change moves computation of transitive scopes to a function `transitiveScopesFor` (and makes it lazy). This opens the door for AOT -> JIT or JIT -> AOT imports, as transitive scopes for AOT modules can be calculated when needed by JIT, and AOT modules can also write expressions that call `transitiveScopesFor` when importing a JIT-compiled module. PR Close #24334 2018-06-06 11:23:38 -07:00			`],`
feat(ivy): first steps towards JIT compilation (#23833) This commit adds a mechanism by which the @angular/core annotations for @Component, @Injectable, and @NgModule become decorators which, when executed at runtime, trigger just-in-time compilation of their associated types. The activation of these decorators is configured by the ivy_switch mechanism, ensuring that the Ivy JIT engine does not get included in Angular bundles unless specifically requested. PR Close #23833 2018-05-09 08:35:25 -07:00			`deps = [`
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488 2018-10-04 13:14:14 -07:00			`":ivy_lib",`
			`"//packages/core/test/render3:domino",`
feat(ivy): first steps towards JIT compilation (#23833) This commit adds a mechanism by which the @angular/core annotations for @Component, @Injectable, and @NgModule become decorators which, when executed at runtime, trigger just-in-time compilation of their associated types. The activation of these decorators is configured by the ivy_switch mechanism, ensuring that the Ivy JIT engine does not get included in Angular bundles unless specifically requested. PR Close #23833 2018-05-09 08:35:25 -07:00			`],`
			`)`