angular-cn/integration/ivy-i18n/tsconfig.legacy.json

{
  "extends": "./tsconfig.app.json",
  "angularCompilerOptions": {
    "enableIvy": true,
    "i18nInFormat": "xlf"
  }
}
test(ivy): i18n - add legacy-id-mode integration test (#32937) PR Close #32937 2019-10-03 06:40:33 -04:00			`{`
			`"extends": "./tsconfig.app.json",`
			`"angularCompilerOptions": {`
			`"enableIvy": true,`
fix(ivy): i18n - turn on legacy message-id support by default (#33053) For v9 we want the migration to the new i18n to be as simple as possible. Previously the developer had to positively choose to use legacy messsage id support in the case that their translation files had not been migrated to the new format by setting the `legacyMessageIdFormat` option in tsconfig.json to the format of their translation files. Now this setting has been changed to `enableI18nLegacyMessageFormat` as is a boolean that defaults to `true`. The format is then read from the `i18nInFormat` option, which was previously used to trigger translations in the pre-ivy angular compiler. PR Close #33053 2019-10-09 07:34:37 -04:00			`"i18nInFormat": "xlf"`
test(ivy): i18n - add legacy-id-mode integration test (#32937) PR Close #32937 2019-10-03 06:40:33 -04:00			`}`
			`}`