Pete Bacon Darwin 2424184d42 feat(compiler): support tokenizing escaped strings (#28055) ... In order to support source mapping of templates, we need to be able to tokenize the template in its original context. When the template is defined inline as a JavaScript string in a TS/JS source file, the tokenizer must be able to handle string escape sequences, such as `\n` and `\"` as they appear in the original source file. This commit teaches the lexer how to unescape these sequences, but only when the `escapedString` option is set to true. Otherwise there is no change to the tokenizing behaviour. PR Close #28055		2019-02-12 20:58:27 -08:00
..
util	test(ivy): update //packages/compiler tests for Ivy (#27301)	2018-11-29 21:31:35 -08:00
BUILD.bazel	test(ivy): update //packages/compiler tests for Ivy (#27301)	2018-11-29 21:31:35 -08: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	refactor(compiler): use `options` argument for parsers (#28055)	2019-02-12 20:58:27 -08:00
html_whitespaces_spec.ts	build: remove `main()` from specs (#21053)	2017-12-22 13:10:51 -08: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	feat(compiler): support tokenizing escaped strings (#28055)	2019-02-12 20:58:27 -08:00