iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/integration/cli-hello-world-ivy-i18n
History
Pete Bacon Darwin f640a4a494 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-10 13:58:30 -07:00
..
e2e test(ivy): i18n - add compile time translation to integration test (#32881) 2019-10-09 13:19:38 -07:00
src fix(ivy): i18n - turn on legacy message-id support by default (#33053) 2019-10-10 13:58:30 -07:00
.editorconfig test(ivy): add cli-hello-world-ivy-i18n integration test (#31609) 2019-08-30 12:53:26 -07:00
README.md test(ivy): add cli-hello-world-ivy-i18n integration test (#31609) 2019-08-30 12:53:26 -07:00
angular.json test(ivy): i18n - add compile time translation to integration test (#32881) 2019-10-09 13:19:38 -07:00
debug-test.sh test(ivy): add cli-hello-world-ivy-i18n integration test (#31609) 2019-08-30 12:53:26 -07:00
package.json test(ivy): i18n - add compile time translation to integration test (#32881) 2019-10-09 13:19:38 -07:00
tsconfig.json test(ivy): add cli-hello-world-ivy-i18n integration test (#31609) 2019-08-30 12:53:26 -07:00
tslint.json test(ivy): add cli-hello-world-ivy-i18n integration test (#31609) 2019-08-30 12:53:26 -07:00
yarn.lock test(ivy): i18n - add compile time translation to integration test (#32881) 2019-10-09 13:19:38 -07:00

README.md

CliHelloWorldIvy

This project was generated with Angular CLI version 7.2.0-rc.0.

Development server

Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.

Build

Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via Protractor.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.