Pete Bacon Darwin 2dc7b45275 fix(compiler): should not break a text token on a non-valid start tag (#42605) ...

Previously the lexer would break out of consuming a text token if it contains
a `<` character. Then if the next characters did not indicate an HTML syntax
item, such as a tag or comment, then it would start a new text token. These
consecutive text tokens are then merged into each other in a post tokenization
step.

In the commit before this, interpolation no longer leaks across text tokens.
The approach given above to handling `<` characters that appear in text is
no longer adequate. This change ensures that the lexer only breaks out of
a text token if the next characters indicate a valid HTML tag, comment,
CDATA etc.

PR Close #42605

2021-06-22 16:37:01 +00:00

..

design

refactor(compiler): remove unused __BUILD_OPTIMIZER_* constants (#41040)

2021-03-04 11:04:27 -08:00

src

fix(compiler): should not break a text token on a non-valid start tag (#42605)

2021-06-22 16:37:01 +00:00

test

fix(compiler): should not break a text token on a non-valid start tag (#42605)

2021-06-22 16:37:01 +00:00

testing

build: update license headers to reference Google LLC (#37205)

2020-05-26 14:26:58 -04:00

BUILD.bazel

build: add npm_integration_test && angular_integration_test (#33927)

2020-02-24 08:59:18 -08:00

compiler.ts

build: update license headers to reference Google LLC (#37205)

2020-05-26 14:26:58 -04:00

index.ts

build: update license headers to reference Google LLC (#37205)

2020-05-26 14:26:58 -04:00

package.json

build(compiler): update supported range of node versions to be less restrictive (#42205)

2021-05-25 17:48:47 +00:00

public_api.ts

build: update license headers to reference Google LLC (#37205)

2020-05-26 14:26:58 -04:00