angular-docs-cn/packages/compiler-cli/test/transformers
Paul Gschwendtner 0ada23a5fb fix(compiler-cli): only pass canonical genfile paths to compiler host (#27062)
In a more specific scenario: Considering people use a custom TypeScript compiler host with `NGC`, they _could_ expect only posix paths in methods like `writeFile`. This at first glance sounds like a trivial issue that should be just fixed by the actual compiler host, but usually TypeScript internal API's just pass around posix normalized paths, and therefore it would be good to follow the same standards when passing JSON genfiles to the `CompilerHost`.

For normal TypeScript files (and TS genfiles), this is already consistent because those will be handled by the actual TypeScript `Program` (see `emitCallback`).

PR Close #27062
2018-11-13 10:51:19 -08:00
..
BUILD.bazel build: remove ivy JIT mode (#26863) 2018-11-02 15:44:05 -07:00
compiler_host_spec.ts fix(compiler): support `.` in import statements. (#20634) 2018-06-13 20:29:22 -07:00
inline_resources_spec.ts fix(compiler-cli): enableResourceInlining handles both styles and styleUrls (#22688) 2018-03-11 22:14:32 -07:00
lower_expressions_spec.ts feat(ivy): @NgModule -> ngInjectorDef compilation (#22458) 2018-03-16 12:57:11 -07:00
metadata_reader_spec.ts refactor(compiler): remove old ngtools api and add listLazyRoutes to new api (#19836) 2017-10-23 18:46:04 -04:00
nocollapse_hack_spec.ts fix(ivy): add @nocollapse when writing closure-annotated code (#25775) 2018-09-11 06:53:21 -07:00
node_emitter_spec.ts build(bazel): use bazel managed node_modules for downstream angular from source build support (#24663) 2018-07-26 17:02:21 -07:00
program_spec.ts fix(compiler-cli): only pass canonical genfile paths to compiler host (#27062) 2018-11-13 10:51:19 -08:00
r3_metadata_transform_spec.ts feat(compiler-cli): reflect static methods added to classes in metadata (#21926) 2018-02-01 08:30:58 -08:00
r3_transform_spec.ts ci(compiler-cli): run compiler-cli tests in bazel (#22997) 2018-03-28 10:02:53 -07:00