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
i18n tool should output the line containing the error #38377
Milestone
Comments
petebacondarwin
added
area: compiler
Issues related to `ngc`, Angular's template compiler
feature
Issue that requests a new feature
labels
Aug 12, 2020
petebacondarwin
added
type: bug/fix
and removed
feature
Issue that requests a new feature
labels
Sep 2, 2020
petebacondarwin
added
state: confirmed
and removed
area: compiler
Issues related to `ngc`, Angular's template compiler
labels
Sep 2, 2020
petebacondarwin
added a commit
to petebacondarwin/angular
that referenced
this issue
Sep 2, 2020
Previously the position of the error in a translation file when parsing it was not displayed. Just the error message. Now the position (line and column) and some context is displayed along with the error messages. Fixes angular#38377
petebacondarwin
added a commit
to petebacondarwin/angular
that referenced
this issue
Sep 2, 2020
Previously the position of the error in a translation file when parsing it was not displayed. Just the error message. Now the position (line and column) and some context is displayed along with the error messages. Fixes angular#38377
petebacondarwin
added a commit
to petebacondarwin/angular
that referenced
this issue
Sep 2, 2020
Previously the position of the error in a translation file when parsing it was not displayed. Just the error message. Now the position (line and column) and some context is displayed along with the error messages. Fixes angular#38377
profanis
pushed a commit
to profanis/angular
that referenced
this issue
Sep 5, 2020
…ar#38673) Previously the position of the error in a translation file when parsing it was not displayed. Just the error message. Now the position (line and column) and some context is displayed along with the error messages. Fixes angular#38377 PR Close angular#38673
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
🐞 Bug report
Is this a regression?
No
Description
We receive translated messages.xlf files back from Smartling which sometimes contain mangled ICUs (missing or added closing brackets, mostly). We have thousands of trans-units, and the angular CLI just outputs
"Error: Invalid ICU message. Missing '}'."
This is true forserve
as well asbuild
Without a reference to the trans-unit or the line in the ICU containing the error, this is a needle in a haystack. Finding it involves combing through the diff one change at a time looking for the ICU that's broken.
🔥 Exception or Error
"Error: Invalid ICU message. Missing '}'."
🌍 Your Environment
The text was updated successfully, but these errors were encountered: