Sonu Kapoor fced8ee40e fix(localize): allow ICU expansion case to start with any character except `}` (#36123) ... Previously, an expansion case could only start with an alpha numeric character. This commit fixes this by allowing an expansion case to start with any character except `}`. The [ICU spec](http://userguide.icu-project.org/formatparse/messages) is pretty vague: > Use a "select" argument to select sub-messages via a fixed set of keywords. It does not specify what can be a "keyword" but from looking at the surrounding syntax it appears that it can indeed be any string that does not contain a `}` character. Closes #31586 PR Close #36123		2020-03-23 11:37:12 -07:00
..
util	test(ivy): update //packages/compiler tests for Ivy (#27301)	2018-11-29 21:31:35 -08:00
BUILD.bazel	build: derive ts_library dep from jasmine_node_test boostrap label if it ends in `_es5` (#34736)	2020-01-15 14:58:07 -05:00
ast_serializer_spec.ts	refactor(compiler): use `options` argument for parsers (#28055)	2019-02-12 20:58:27 -08:00
ast_spec_utils.ts	build: update npm dependencies (#19328)	2017-09-22 13:20:52 -07:00
html_parser_spec.ts	fix(localize): allow ICU expansion case to start with any character except `}` (#36123)	2020-03-23 11:37:12 -07:00
html_whitespaces_spec.ts	fix(compiler): do not remove whitespace wrapping i18n expansions (#31962)	2019-08-09 12:03:50 -07:00
icu_ast_expander_spec.ts	refactor(compiler): use `options` argument for parsers (#28055)	2019-02-12 20:58:27 -08:00
lexer_spec.ts	fix(compiler): do not remove whitespace wrapping i18n expansions (#31962)	2019-08-09 12:03:50 -07:00