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

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

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

ts_library(
    name = "file_system",
    srcs = ["index.ts"] + glob([
        "src/*.ts",
    ]),
    deps = [
        "//packages:types",
        "@npm//@types/node",
        "@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			`package(default_visibility = ["//visibility:public"])`

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

			`ts_library(`
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			`name = "file_system",`
style: enforce buildifier lint on CI (#28186) PR Close #28186 2019-02-26 13:30:44 +01:00			`srcs = ["index.ts"] + glob([`
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			`"src/*.ts",`
			`]),`
			`deps = [`
			`"//packages:types",`
build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871) PR Close #28871 2019-02-20 09:54:42 -08:00			`"@npm//@types/node",`
			`"@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			`],`
			`)`