-
Notifications
You must be signed in to change notification settings - Fork 26.3k
fix(compiler): ignore placeholder-only i18n messages #58154
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
Conversation
Message which only contain a single placeholder cannot be translated, there is no static text to be translated. Therefore these messages can be skipped and shouldn't be extracted at all. Ideally, Angular would throw an error if a message is only a placeholder, since it should not contain an `i18n` attribute at all. However this would be a breaking change and require a migration which isn't in scope right now. We can explore converting this to a hard error sometime in the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
Note that this change is not gated on any flag and is currently targeting patch.
If we think that's too risky, I can put it behind a flag or target major.
I think it might be an unexpected change in behavior for a patch release, so we can target a major release instead.
Updated to |
This PR was merged into the repository by commit ba43408. The changes were merged into the following branches: main |
Fixes some tests that started failing, because angular#58154 made it so placeholder-only messages are extracted while angular#58176 added some tests that only contain placeholders.
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. |
Message which only contain a single placeholder cannot be translated, there is no static text to be translated. Therefore these messages can be skipped and shouldn't be extracted at all.
Ideally, Angular would throw an error if a message is only a placeholder, since it should not contain an
i18n
attribute at all. However this would be a breaking change and require a migration which isn't in scope right now. We can explore converting this to a hard error sometime in the future.Note that this change is not gated on any flag and is currently targeting
patch
. I think this is reasonable because placeholder-only messages are useless to extract, but it is an observable behavior change. If we think that's too risky, I can put it behind a flag or targetmajor
.