-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ng serve should watch i18n messages files #16341
Comments
it's still an issue with v10 :( I would also re-qualify it from |
…h dev server When using i18n with the dev server, the translation files will now be linked as a dependency to any file containing translated text. This allows translation files to be watched and the application to be rebuilt using the changed translation files. This change should also provide some performance improvements as well since now only files containing `$localize` will be parsed and processed by the babel-based localization inliner. Closes angular#16341
…h dev server When using i18n with the dev server, the translation files will now be linked as a dependency to any file containing translated text. This allows translation files to be watched and the application to be rebuilt using the changed translation files. This change should also provide some performance improvements as well since now only files containing `$localize` will be parsed and processed by the babel-based localization inliner. Closes angular#16341
…h dev server When using i18n with the dev server, the translation files will now be linked as a dependency to any file containing translated text. This allows translation files to be watched and the application to be rebuilt using the changed translation files. This change should also provide some performance improvements as well since now only files containing `$localize` will be parsed and processed by the babel-based localization inliner. Closes angular#16341
…h dev server When using i18n with the dev server, the translation files will now be linked as a dependency to any file containing translated text. This allows translation files to be watched and the application to be rebuilt using the changed translation files. This change should also provide some performance improvements as well since now only files containing `$localize` will be parsed and processed by the babel-based localization inliner. Closes angular#16341
…h dev server When using i18n with the dev server, the translation files will now be linked as a dependency to any file containing translated text. This allows translation files to be watched and the application to be rebuilt using the changed translation files. This change should also provide some performance improvements as well since now only files containing `$localize` will be parsed and processed by the babel-based localization inliner. Closes angular#16341
I have to restart my dev server when changing anything in the .xlf files to see the change reflected in the server. Is this issue related? |
@clydin sorry to bother you, but I just saw that you have a PR that address this issue... so allow me to kindly ask: is there a plan to merge this before v13 comes out? If not, does anyone know if there's any workaround available? Currently is too tedious to restart server to see the changes in the file. Thanks. |
Unfortunately, the referenced PR is not complete and will not be available in 13.0 but should be available in an upcoming v13 minor release. |
…h dev server When using i18n with the dev server, the translation files will now be linked as a dependency to any file containing translated text. This allows translation files to be watched and the application to be rebuilt using the changed translation files. This change should also provide some performance improvements as well since now only files containing `$localize` will be parsed and processed by the babel-based localization inliner. Closes angular#16341
…h dev server When using i18n with the dev server, the translation files will now be linked as a dependency to any file containing translated text. This allows translation files to be watched and the application to be rebuilt using the changed translation files. This change should also provide some performance improvements as well since now only files containing `$localize` will be parsed and processed by the babel-based localization inliner. Closes angular#16341
…h dev server When using i18n with the dev server, the translation files will now be linked as a dependency to any file containing translated text. This allows translation files to be watched and the application to be rebuilt using the changed translation files. This change should also provide some performance improvements as well since now only files containing `$localize` will be parsed and processed by the babel-based localization inliner. Closes angular#16341
…h dev server When using i18n with the dev server, the translation files will now be linked as a dependency to any file containing translated text. This allows translation files to be watched and the application to be rebuilt using the changed translation files. This change should also provide some performance improvements as well since now only files containing `$localize` will be parsed and processed by the babel-based localization inliner. Closes angular#16341
…h dev server When using i18n with the dev server, the translation files will now be linked as a dependency to any file containing translated text. This allows translation files to be watched and the application to be rebuilt using the changed translation files. This change should also provide some performance improvements as well since now only files containing `$localize` will be parsed and processed by the babel-based localization inliner. Closes angular#16341
…h dev server When using i18n with the dev server, the translation files will now be linked as a dependency to any file containing translated text. This allows translation files to be watched and the application to be rebuilt using the changed translation files. Closes angular#16341
…h dev server When using i18n with the dev server, the translation files will now be linked as a dependency to any file containing translated text. This allows translation files to be watched and the application to be rebuilt using the changed translation files. Closes #16341
Is anyone else having an issue with this change now giving a warning every time you save a file that every message in your translation file is a duplicate?
every time I save a file while running |
Yes I don't like the idea of suppressing the warning; my concern isn't seeing the warnings, it is that they only appear after a watched file rebuilds. I am not getting the warnings on the initial builds. It seems like the variable isn't being properly re-initialized. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
🚀 Feature request
Command (mark with an
x
)Description
When using the new i18n support with CLI v9 (rc.4 at the time of writing), it is possible to run:
with
fr
:This works great, but does not pick up translation changes in
messages.fr.xlf
, requiring a stop and restart ofng serve
.Describe the solution you'd like
It would be nice to have
ng serve
watch the files defined in thelocales
configuration.Describe alternatives you've considered
It is possible to stop and restart the server to have the up-to-date translations.
The text was updated successfully, but these errors were encountered: