-
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
--localize: pipes localization missing for default language if it's not English #16389
Comments
Already known issue in <=rc4, it works for english because it is default locale. Apparently CLI doesn’t handle source locale different than « en-US ». As workaround you can register it manually (see aio doc) |
@elvisbegovic I don't have the time to debug this, but if the CLI can handle it when the order is different, I think it can handle it in any order. From what I see, it's just a wrong condition or a missed case, the code to add the pipes localization already exists. But maybe I'm unaware of an unexpected limitation. |
This is a defect and will be corrected before the final release. |
…cted when localizing Fixes angular#16389
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. |
🐞 Bug report
Command
Is this a regression?
No, as it's a new feature in v9.
Description
When using the new
--localize
option, if the default language (sourceLocale
) is not English, localization for pipes is missing in the default language, resulting the app to fail.🔬 Minimal Reproduction
date
angular.json
:ng build --prod --localize
Result:
en
andde
will work fine, butfr
won't have localization for pipes.If English is the default like below, every locale will work fine:
🔥 Exception or Error
In browser console:
Resulting in everything after the pipe in the template to fail to render.
🌍 Your Environment
The text was updated successfully, but these errors were encountered: