angular-docs-cn/packages/compiler-cli/test/helpers/index.ts

/**
 * @license
 * Copyright Google LLC All Rights Reserved.
 *
 * Use of this source code is governed by an MIT-style license that can be
 * found in the LICENSE file at https://angular.io/license
 */
export {getAngularPackagesFromRunfiles, resolveNpmTreeArtifact} from './src/runfile_helpers';
export * from './src/mock_file_loading';
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			`/**`
			`* @license`
build: update license headers to reference Google LLC (#37205) Update the license headers throughout the repository to reference Google LLC rather than Google Inc, for the required license headers. PR Close #37205 2020-05-19 12:08:49 -07:00			`* Copyright Google LLC All Rights Reserved.`
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			`*`
			`* Use of this source code is governed by an MIT-style license that can be`
			`* found in the LICENSE file at https://angular.io/license`
			`*/`
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			`export {getAngularPackagesFromRunfiles, resolveNpmTreeArtifact} from './src/runfile_helpers';`
			`export * from './src/mock_file_loading';`