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

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

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

ts_library(
    name = "test_lib",
    testonly = True,
    srcs = glob([
        "**/*.ts",
    ]),
    deps = [
        "//packages/compiler-cli/src/ngtsc/file_system",
        "//packages/compiler-cli/src/ngtsc/file_system/testing",
        "@npm//typescript",
    ],
)

jasmine_node_test(
    name = "test",
    bootstrap = ["//tools/testing:node_no_angular_es5"],
    deps = [
        ":test_lib",
    ],
)
feat(ivy): introduce concrete types for paths in ngtsc (#28523) This commit introduces a new ngtsc sub-library, 'path', which contains branded string types for the different kind of paths that ngtsc manipulates. Having static types for these paths will reduce the number of path-related bugs (especially on Windows) and will eliminate unnecessary defensive normalizing. See the README.md file for more detail. PR Close #28523 2019-02-01 10:07:34 -08:00			`load("//tools:defaults.bzl", "jasmine_node_test", "ts_library")`

refactor(compiler-cli): tidy up file_system BUILD.bazel file_system (#37114) * Re-order the `load` and `package` statements * Make `srcs` glob more generic * Remove unnecessary dependencies PR Close #37114 2020-06-20 08:49:32 +01:00			`package(default_visibility = ["//visibility:public"])`

feat(ivy): introduce concrete types for paths in ngtsc (#28523) This commit introduces a new ngtsc sub-library, 'path', which contains branded string types for the different kind of paths that ngtsc manipulates. Having static types for these paths will reduce the number of path-related bugs (especially on Windows) and will eliminate unnecessary defensive normalizing. See the README.md file for more detail. PR Close #28523 2019-02-01 10:07:34 -08:00			`ts_library(`
			`name = "test_lib",`
			`testonly = True,`
			`srcs = glob([`
			`"*/.ts",`
			`]),`
			`deps = [`
refactor(ivy): implement a virtual file-system layer in ngtsc + ngcc (#30921) To improve cross platform support, all file access (and path manipulation) is now done through a well known interface (`FileSystem`). For testing a number of `MockFileSystem` implementations are provided. These provide an in-memory file-system which emulates operating systems like OS/X, Unix and Windows. The current file system is always available via the static method, `FileSystem.getFileSystem()`. This is also used by a number of static methods on `AbsoluteFsPath` and `PathSegment`, to avoid having to pass `FileSystem` objects around all the time. The result of this is that one must be careful to ensure that the file-system has been initialized before using any of these static methods. To prevent this happening accidentally the current file system always starts out as an instance of `InvalidFileSystem`, which will throw an error if any of its methods are called. You can set the current file-system by calling `FileSystem.setFileSystem()`. During testing you can call the helper function `initMockFileSystem(os)` which takes a string name of the OS to emulate, and will also monkey-patch aspects of the TypeScript library to ensure that TS is also using the current file-system. Finally there is the `NgtscCompilerHost` to be used for any TypeScript compilation, which uses a given file-system. All tests that interact with the file-system should be tested against each of the mock file-systems. A series of helpers have been provided to support such tests: * `runInEachFileSystem()` - wrap your tests in this helper to run all the wrapped tests in each of the mock file-systems. * `addTestFilesToFileSystem()` - use this to add files and their contents to the mock file system for testing. * `loadTestFilesFromDisk()` - use this to load a mirror image of files on disk into the in-memory mock file-system. * `loadFakeCore()` - use this to load a fake version of `@angular/core` into the mock file-system. All ngcc and ngtsc source and tests now use this virtual file-system setup. PR Close #30921 2019-06-06 20:22:32 +01:00			`"//packages/compiler-cli/src/ngtsc/file_system",`
			`"//packages/compiler-cli/src/ngtsc/file_system/testing",`
fix(ivy): ngtsc - NgtscCompilerHost should cope with directories that look like files (#31289) The TS compiler is likely to test paths with extensions and try to load them as files. Therefore `fileExists()` and methods that rely on it need to be able to distinguish between real files and directories that have paths that look like files. This came up as a bug in ngcc when trying to process `ngx-virtual-scroller`, which relies upon a library called `@tweenjs/tween.js`. PR Close #31289 2019-06-26 17:01:43 +01:00			`"@npm//typescript",`
feat(ivy): introduce concrete types for paths in ngtsc (#28523) This commit introduces a new ngtsc sub-library, 'path', which contains branded string types for the different kind of paths that ngtsc manipulates. Having static types for these paths will reduce the number of path-related bugs (especially on Windows) and will eliminate unnecessary defensive normalizing. See the README.md file for more detail. PR Close #28523 2019-02-01 10:07:34 -08:00			`],`
			`)`

			`jasmine_node_test(`
			`name = "test",`
test: handle bootstrap templated_args in jasmine_node_test defaults.bzl (#34736) PR Close #34736 2020-01-07 23:56:49 -08:00			`bootstrap = ["//tools/testing:node_no_angular_es5"],`
feat(ivy): introduce concrete types for paths in ngtsc (#28523) This commit introduces a new ngtsc sub-library, 'path', which contains branded string types for the different kind of paths that ngtsc manipulates. Having static types for these paths will reduce the number of path-related bugs (especially on Windows) and will eliminate unnecessary defensive normalizing. See the README.md file for more detail. PR Close #28523 2019-02-01 10:07:34 -08:00			`deps = [`
			`":test_lib",`
			`],`
			`)`