Previously only one translation file per locale could be loaded. Now the user can specify multiple files per locale, and the translations from each of these files will be merged together by message id. The merging is on a first-wins approach. So if to you have three files to be merged: ``` ['a.xlf', 'b.xmb', 'c.json'] ``` Then any message from `a.xlf` will be used rather than a message from `b.xmb` or `c.json` and so on. In practice this means that you should put the files in order of most important first, with "fallback" translations later. PR Close #36792
33 lines
976 B
TypeScript
33 lines
976 B
TypeScript
import {AppPage} from '../app.po';
|
|
|
|
describe('cli-hello-world-ivy App', () => {
|
|
let page: AppPage;
|
|
beforeEach(() => {
|
|
page = new AppPage();
|
|
page.navigateTo();
|
|
});
|
|
|
|
it('should display title', () => {
|
|
expect(page.getHeading()).toEqual('Guten Tag, cli-hello-world-ivy-compat! (inline)');
|
|
});
|
|
|
|
it('should display welcome message', () => {
|
|
expect(page.getParagraph('message')).toEqual('Willkommen in der i18n App. (inline)');
|
|
});
|
|
|
|
it('should display extra message', () => {
|
|
expect(page.getParagraph('extra')).toEqual('Zusätzliche Nachricht');
|
|
});
|
|
|
|
it('should display the locale', () => {
|
|
expect(page.getParagraph('locale')).toEqual('de');
|
|
});
|
|
|
|
// TODO : Re-enable when CLI translation inlining supports locale inlining (and so we can use it
|
|
// to load the correct locale data)
|
|
xit('the date pipe should show the localized month', () => {
|
|
page.navigateTo();
|
|
expect(page.getParagraph('date')).toEqual('Januar');
|
|
});
|
|
});
|