You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
i18n: numbers for select-icu fail to compile (template parse error) #17799
[ ] Regression (behavior that used to work and stopped working in a new release)
[ x ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
Current behavior
Given this code {gender, select, m {male} f {female}} the app compiles correctly.
Changing it to a number ({gender, select, 1 {male} f {female}} fails with a template parse error:
Unexpected character "EOF" (Do you have an unescaped "{" in your template? Use "{{ '{' }}") to escape it.) ("
<br /><br />
</div>[ERROR ->]"): ng:///ThemeModule/ThemeComponent.html@46:6
Invalid ICU message. Missing '}'. ("
SELECT START {gender, select, [ERROR ->]1 {male} f {female}} SELECT END
</span>
<div>
"): ng:///ThemeModule/ThemeComponent.html@6:31
Invalid ICU message. Missing '}'. ("
<br /><br />
</div>[ERROR ->]"): ng:///ThemeModule/ThemeComponent.html@46:6
Expected behavior
Should handle numbers as strings and display correctly.
Minimal reproduction of the problem with instructions
Drop in the example from above in any working ng4-project.
Please tell us about your environment
Angular version: 4.2.4
Browser: Chrome (Windows 10) version 58
Activity
fix(compiler): allow numbers for ICU message cases in lexer (#18095)
fix(compiler): allow numbers for ICU message cases in lexer (angular#…
fix(compiler): allow numbers for ICU message cases in lexer (angular#…
fix(compiler): allow numbers for ICU message cases in lexer (angular#…
angular-automatic-lock-bot commentedon Sep 12, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.