angular/packages/localize
Pete Bacon Darwin 3150f9f66d fix(localize): relax error to warning for missing target (#41944)
Some localization workflows want to use the extracted source translation
files directy back in the project as a target translation file.

The extraction process generates files that only contain "source" messages
and not "target" messages. This is actually valid for most translation formats
but currently the Angular localization process expects target translation files
to always contain target messages and will stop with an error in this case.

Now, instead of an error, the translation file loader will log a warning,
and then try to falback to a source message, only erroring if this is also
missing.

Fixes #21690

PR Close #41944
2021-05-04 21:05:55 -07:00
..
init docs(localize): expose documentation for the @angular/localize package (#40317) 2021-03-19 12:36:10 -07:00
schematics fix(localize): update type castings for JSON.parse usage (#40710) 2021-02-09 10:48:46 -08:00
src fix(localize): relax error to warning for missing target (#41944) 2021-05-04 21:05:55 -07:00
test build: update license headers to reference Google LLC (#37205) 2020-05-26 14:26:58 -04:00
BUILD.bazel build: provide full paths to ts_api_guardian_test_npm_package and ts_api_guardian_test (#36034) 2020-03-12 09:49:00 -07:00
index.ts build: update license headers to reference Google LLC (#37205) 2020-05-26 14:26:58 -04:00
localize.ts build: update license headers to reference Google LLC (#37205) 2020-05-26 14:26:58 -04:00
package.json build: update yargs dependency to 16.2.0. (#41392) 2021-04-01 13:41:26 -07:00
PACKAGE.md docs(localize): expose documentation for the @angular/localize package (#40317) 2021-03-19 12:36:10 -07:00
private.ts build: update license headers to reference Google LLC (#37205) 2020-05-26 14:26:58 -04:00