Pete Bacon Darwin 357aa4a097 fix(ivy): i18n - use `MessageId` for matching translations (#32594) ... As discussed in https://hackmd.io/33M5Wb-JT7-0fneA0JuHPA `SourceMessage` strings are not sufficient for matching translations. This commit updates `@angular/localize` to use `MessageId`s for translation matching instead. Also the run-time translation will now log a warning to the console if a translation is missing. BREAKING CHANGE: Translations (loaded via the `loadTranslations()` function) must now use `MessageId` for the translation key rather than the previous `SourceMessage` string. PR Close #32594		2019-09-17 09:17:44 -07:00
..
init	feat(ivy): i18n - add syntax support for `$localize` metadata block (#32594)	2019-09-17 09:17:44 -07:00
src	fix(ivy): i18n - use `MessageId` for matching translations (#32594)	2019-09-17 09:17:44 -07:00
test	fix(ivy): i18n - use `MessageId` for matching translations (#32594)	2019-09-17 09:17:44 -07:00
BUILD.bazel	fix(ivy): i18n - use `MessageId` for matching translations (#32594)	2019-09-17 09:17:44 -07:00
index.ts	feat(ivy): i18n - add syntax support for `$localize` metadata block (#32594)	2019-09-17 09:17:44 -07:00
localize.ts	feat(ivy): i18n - reorganize entry-points for better reuse (#32488)	2019-09-12 15:35:34 -07:00
package.json	feat(ivy): i18n - reorganize entry-points for better reuse (#32488)	2019-09-12 15:35:34 -07:00