angular-cn/packages/compiler-cli/test/ngtsc
Olivier Combe 91c7b451d5 feat(ivy): support i18n without closure (#28689)
So far using runtime i18n with ivy meant that you needed to use Closure and `goog.getMsg` (or a polyfill). This PR changes the compiler to output both closure & non-closure code, while the unused option will be tree-shaken by minifiers.
This means that if you use the Angular CLI with ivy and load a translations file, you can use i18n and the application will not throw at runtime.
For now it will not translate your application, but at least you can try ivy without having to remove all of your i18n code and configuration.
PR Close #28689
2019-04-11 08:28:45 -07:00
..
fake_core refactor(ivy): prefix all generated instructions (#29692) 2019-04-10 12:11:40 -07:00
BUILD.bazel build(bazel): back out of @bazel/jasmine 0.27.7 with shard count (#29444) 2019-03-21 09:59:13 -07:00
env.ts test(ivy): support multiple compilations in the ngtsc test env (#29380) 2019-04-01 15:13:56 -07:00
incremental_spec.ts perf(ivy): basic incremental compilation for ngtsc (#29380) 2019-04-01 15:13:56 -07:00
ngtsc_spec.ts feat(ivy): support i18n without closure (#28689) 2019-04-11 08:28:45 -07:00
scope_spec.ts refactor(ivy): prefix all generated instructions (#29692) 2019-04-10 12:11:40 -07:00
sourcemap_utils.ts feat(ivy): add source mappings to compiled Angular templates (#28055) 2019-02-12 20:58:28 -08:00
template_mapping_spec.ts refactor(ivy): prefix all generated instructions (#29692) 2019-04-10 12:11:40 -07:00
template_typecheck_spec.ts refactor(ivy): prefix all generated instructions (#29692) 2019-04-10 12:11:40 -07:00