angular-cn/packages/compiler-cli/test/ngtsc/BUILD.bazel

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

ts_library(
    name = "ngtsc_lib",
    testonly = True,
    srcs = glob(["**/*.ts"]),
    deps = [
        "//packages/compiler",
        "//packages/compiler-cli",
        "//packages/compiler-cli/src/ngtsc/routing",
        "//packages/compiler-cli/src/ngtsc/util",
        "//packages/compiler-cli/test:test_utils",
        "@ngdeps//@types/source-map",
        "@ngdeps//source-map",
        "@ngdeps//typescript",
    ],
)

jasmine_node_test(
    name = "ngtsc",
    bootstrap = ["angular/tools/testing/init_node_no_angular_spec.js"],
    data = [
        "//packages/compiler-cli/test/ngtsc/fake_core:npm_package",
    ],
    deps = [
        ":ngtsc_lib",
        "//tools/testing:node_no_angular",
        "@ngdeps//minimist",
    ],
)
build(bazel): update to rules_typescript 0.17.0 & rules_nodejs 0.13.4 (#25920) PR Close #25920 2018-09-11 18:11:32 -07:00			`load("//tools:defaults.bzl", "jasmine_node_test", "ts_library")`
feat(ivy): first steps towards ngtsc mode (#23455) This commit adds a new compiler pipeline that isn't dependent on global analysis, referred to as 'ngtsc'. This new compiler is accessed by running ngc with "enableIvy" set to "ngtsc". It reuses the same initialization logic but creates a new implementation of Program which does not perform the global-level analysis that AngularCompilerProgram does. It will be the foundation for the production Ivy compiler. PR Close #23455 2018-04-06 09:53:10 -07:00
			`ts_library(`
			`name = "ngtsc_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,`
test(ivy): refactor ngtsc tests to use an NgtscTestEnvironment helper (#26203) This commit gets ready for the introduction of ngtsc template type-checking tests by refactoring test environment setup into a custom helper. This helper will simplify the authoring of future ngtsc tests. Ngtsc tests previously returned a numeric error code (a la ngtsc's CLI interface) if any TypeScript errors occurred. The helper has the ability to run ngtsc and return the actual array of ts.Diagnostics, which greatly increases the ability to write clean tests. PR Close #26203 2018-09-25 15:35:03 -07:00			`srcs = glob(["*/.ts"]),`
feat(ivy): first steps towards ngtsc mode (#23455) This commit adds a new compiler pipeline that isn't dependent on global analysis, referred to as 'ngtsc'. This new compiler is accessed by running ngc with "enableIvy" set to "ngtsc". It reuses the same initialization logic but creates a new implementation of Program which does not perform the global-level analysis that AngularCompilerProgram does. It will be the foundation for the production Ivy compiler. PR Close #23455 2018-04-06 09:53:10 -07:00			`deps = [`
			`"//packages/compiler",`
			`"//packages/compiler-cli",`
test(ivy): introduce route testing mode for ngtsc tests (#27697) This commit introduces a new mode for the NgtscTestEnvironment which builds the NgtscProgram and then asks for the list of lazy routes, instead of running the TS emit phase. PR Close #27697 2018-11-16 17:54:43 +01:00			`"//packages/compiler-cli/src/ngtsc/routing",`
feat(ivy): add source mappings to compiled Angular templates (#28055) During analysis, the `ComponentDecoratorHandler` passes the component template to the `parseTemplate()` function. Previously, there was little or no information about the original source file, where the template is found, passed when calling this function. Now, we correctly compute the URL of the source of the template, both for external `templateUrl` and in-line `template` cases. Further in the in-line template case we compute the character range of the template in its containing source file; but only in the case that the template is a simple string literal. If the template is actually a dynamic value like an interpolated string or a function call, then we do not try to add the originating source file information. The translator that converts Ivy AST nodes to TypeScript now adds these template specific source mappings, which account for the file where the template was found, to the templates to support stepping through the template creation and update code when debugging an Angular application. Note that some versions of TypeScript have a bug which means they cannot support external template source-maps. We check for this via the `canSourceMapExternalTemplates()` helper function and avoid trying to add template mappings to external templates if not supported. PR Close #28055 2019-02-08 22:10:21 +00:00			`"//packages/compiler-cli/src/ngtsc/util",`
feat(ivy): first steps towards ngtsc mode (#23455) This commit adds a new compiler pipeline that isn't dependent on global analysis, referred to as 'ngtsc'. This new compiler is accessed by running ngc with "enableIvy" set to "ngtsc". It reuses the same initialization logic but creates a new implementation of Program which does not perform the global-level analysis that AngularCompilerProgram does. It will be the foundation for the production Ivy compiler. PR Close #23455 2018-04-06 09:53:10 -07:00			`"//packages/compiler-cli/test:test_utils",`
feat(ivy): add source mappings to compiled Angular templates (#28055) During analysis, the `ComponentDecoratorHandler` passes the component template to the `parseTemplate()` function. Previously, there was little or no information about the original source file, where the template is found, passed when calling this function. Now, we correctly compute the URL of the source of the template, both for external `templateUrl` and in-line `template` cases. Further in the in-line template case we compute the character range of the template in its containing source file; but only in the case that the template is a simple string literal. If the template is actually a dynamic value like an interpolated string or a function call, then we do not try to add the originating source file information. The translator that converts Ivy AST nodes to TypeScript now adds these template specific source mappings, which account for the file where the template was found, to the templates to support stepping through the template creation and update code when debugging an Angular application. Note that some versions of TypeScript have a bug which means they cannot support external template source-maps. We check for this via the `canSourceMapExternalTemplates()` helper function and avoid trying to add template mappings to external templates if not supported. PR Close #28055 2019-02-08 22:10:21 +00:00			`"@ngdeps//@types/source-map",`
			`"@ngdeps//source-map",`
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488 2018-10-04 13:14:14 -07:00			`"@ngdeps//typescript",`
feat(ivy): first steps towards ngtsc mode (#23455) This commit adds a new compiler pipeline that isn't dependent on global analysis, referred to as 'ngtsc'. This new compiler is accessed by running ngc with "enableIvy" set to "ngtsc". It reuses the same initialization logic but creates a new implementation of Program which does not perform the global-level analysis that AngularCompilerProgram does. It will be the foundation for the production Ivy compiler. PR Close #23455 2018-04-06 09:53:10 -07:00			`],`
			`)`

			`jasmine_node_test(`
			`name = "ngtsc",`
			`bootstrap = ["angular/tools/testing/init_node_no_angular_spec.js"],`
			`data = [`
			`"//packages/compiler-cli/test/ngtsc/fake_core:npm_package",`
			`],`
			`deps = [`
			`":ngtsc_lib",`
			`"//tools/testing:node_no_angular",`
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488 2018-10-04 13:14:14 -07:00			`"@ngdeps//minimist",`
feat(ivy): first steps towards ngtsc mode (#23455) This commit adds a new compiler pipeline that isn't dependent on global analysis, referred to as 'ngtsc'. This new compiler is accessed by running ngc with "enableIvy" set to "ngtsc". It reuses the same initialization logic but creates a new implementation of Program which does not perform the global-level analysis that AngularCompilerProgram does. It will be the foundation for the production Ivy compiler. PR Close #23455 2018-04-06 09:53:10 -07:00			`],`
			`)`