Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fixup! test: update ivy i18n integration test
- Loading branch information
1 parent
19ca362
commit 35fbd2c
Showing
6 changed files
with
105 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
86 changes: 86 additions & 0 deletions
86
integration/cli-hello-world-ivy-i18n/src/polyfills-runtime.ts
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,86 @@ | ||
| /** | ||
| * This file includes polyfills needed by Angular and is loaded before the app. | ||
| * You can add your own extra polyfills to this file. | ||
| * | ||
| * This file is divided into 2 sections: | ||
| * 1. Browser polyfills. These are applied before loading ZoneJS and are sorted by browsers. | ||
| * 2. Application imports. Files imported after ZoneJS that should be loaded before your main | ||
| * file. | ||
| * | ||
| * The current setup is for so-called "evergreen" browsers; the last versions of browsers that | ||
| * automatically update themselves. This includes Safari >= 10, Chrome >= 55 (including Opera), | ||
| * Edge >= 13 on the desktop, and iOS 10 and Chrome on mobile. | ||
| * | ||
| * Learn more in https://angular.io/guide/browser-support | ||
| */ | ||
|
|
||
| /*************************************************************************************************** | ||
| * BROWSER POLYFILLS | ||
| */ | ||
|
|
||
| /** IE10 and IE11 requires the following for NgClass support on SVG elements */ | ||
| // import 'classlist.js'; // Run `npm install --save classlist.js`. | ||
|
|
||
| /** | ||
| * Web Animations `@angular/platform-browser/animations` | ||
| * Only required if AnimationBuilder is used within the application and using IE/Edge or Safari. | ||
| * Standard animation support in Angular DOES NOT require any polyfills (as of Angular 6.0). | ||
| */ | ||
| // import 'web-animations-js'; // Run `npm install --save web-animations-js`. | ||
|
|
||
| /** | ||
| * By default, zone.js will patch all possible macroTask and DomEvents | ||
| * user can disable parts of macroTask/DomEvents patch by setting following flags | ||
| * because those flags need to be set before `zone.js` being loaded, and webpack | ||
| * will put import in the top of bundle, so user need to create a separate file | ||
| * in this directory (for example: zone-flags.ts), and put the following flags | ||
| * into that file, and then add the following code before importing zone.js. | ||
| * import './zone-flags.ts'; | ||
| * | ||
| * The flags allowed in zone-flags.ts are listed here. | ||
| * | ||
| * The following flags will work for all browsers. | ||
| * | ||
| * (window as any).__Zone_disable_requestAnimationFrame = true; // disable patch | ||
| * requestAnimationFrame | ||
| * (window as any).__Zone_disable_on_property = true; // disable patch onProperty such as onclick | ||
| * (window as any).__zone_symbol__UNPATCHED_EVENTS = ['scroll', 'mousemove']; // disable patch | ||
| * specified eventNames | ||
| * | ||
| * in IE/Edge developer tools, the addEventListener will also be wrapped by zone.js | ||
| * with the following flag, it will bypass `zone.js` patch for IE/Edge | ||
| * | ||
| * (window as any).__Zone_enable_cross_context_check = true; | ||
| * | ||
| */ | ||
|
|
||
| /*************************************************************************************************** | ||
| * Zone JS is required by default for Angular itself. | ||
| */ | ||
| import 'zone.js/dist/zone'; // Included with Angular CLI. | ||
|
|
||
| /*************************************************************************************************** | ||
| * Load `$localize` onto the global scope - used if i18n tags appear in Angular templates. | ||
| */ | ||
| import '@angular/localize/init'; | ||
|
|
||
| // Note that `computeMsgId` is a private API at this stage. It will probably be exported directly | ||
| // from `@angular/localize` at some point. | ||
| import {computeMsgId} from '@angular/compiler'; | ||
| import {loadTranslations} from '@angular/localize'; | ||
|
|
||
| // Load some runtime translations! | ||
| loadTranslations({ | ||
| [computeMsgId(' Hello {$INTERPOLATION}! ')]: 'Bonjour {$INTERPOLATION}!', | ||
| [computeMsgId('Welcome to the i18n app.')]: 'Bienvenue sur l\'application i18n.', | ||
| }); | ||
|
|
||
| // Set up the locale for the runtime inlining (EXPERIMENTAL) | ||
| $localize.locale = 'fr'; | ||
| import {registerLocaleData} from '@angular/common'; | ||
| import localeFr from '@angular/common/locales/fr'; | ||
| registerLocaleData(localeFr); | ||
|
|
||
| /*************************************************************************************************** | ||
| * APPLICATION IMPORTS | ||
| */ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters