angular-docs-cn/packages/compiler/test/ml_parser
Joey Perrott ff9f4de4f1 fix(compiler): update unparsable character reference entity error messages (#38319)
Within an angular template, when a character entity is unable to be parsed, previously a generic
unexpected character error was thrown.  This does not properly express the issue that was discovered
as the issue is actually caused by the discovered character making the whole of the entity unparsable.
The compiler will now instead inform via the error message what string was attempted to be parsed
and what it was attempted to be parsed as.

Example, for this template:
```
<p>
  &#x123p
</p>
```
Before this change:
`Unexpected character "p"`

After this change:
`Unable to parse entity "&#x123p" - hexadecimal character reference entities must end with ";"`

Fixes #26067

PR Close #38319
2020-07-31 15:32:53 -07:00
..
util build: update license headers to reference Google LLC (#37205) 2020-05-26 14:26:58 -04: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 build: update license headers to reference Google LLC (#37205) 2020-05-26 14:26:58 -04:00
ast_spec_utils.ts fix(compiler): properly associate source spans for implicitly closed elements (#38126) 2020-07-20 10:02:06 -07:00
html_parser_spec.ts fix(compiler): properly associate source spans for implicitly closed elements (#38126) 2020-07-20 10:02:06 -07:00
html_whitespaces_spec.ts build: update license headers to reference Google LLC (#37205) 2020-05-26 14:26:58 -04:00
icu_ast_expander_spec.ts build: update license headers to reference Google LLC (#37205) 2020-05-26 14:26:58 -04:00
lexer_spec.ts fix(compiler): update unparsable character reference entity error messages (#38319) 2020-07-31 15:32:53 -07:00