af95dddd7e
A quirk of the Angular template parser is that when parsing templates in the "default" mode, with options specified by the user, the source mapping information in the template AST may be inaccurate. As a result, the compiler parses the template twice: once for "emit" and once to produce an AST with accurate sourcemaps for diagnostic production. Previously, only the first parse was performed during analysis. The second parse occurred during the template type-checking phase, just in time to produce the template type-checking file. However, with the reuse of analysis results during incremental builds, it makes more sense to do the diagnostic parse eagerly during analysis so that the work isn't unnecessarily repeated in subsequent builds. This commit refactors the `ComponentDecoratorHandler` to do both parses eagerly, which actually cleans up some complexity around template parsing as well. PR Close #34334 |
||
---|---|---|
.circleci | ||
.devcontainer | ||
.github | ||
.vscode | ||
aio | ||
docs | ||
integration | ||
modules | ||
packages | ||
scripts | ||
third_party | ||
tools | ||
.bazelignore | ||
.bazelrc | ||
.clang-format | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
.nvmrc | ||
BUILD.bazel | ||
CHANGELOG.md | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
LICENSE | ||
README.md | ||
WORKSPACE | ||
browser-providers.conf.js | ||
gulpfile.js | ||
karma-js.conf.js | ||
package.json | ||
protractor-perf.conf.js | ||
shims_for_IE.js | ||
test-events.js | ||
test-main.js | ||
tslint.json | ||
yarn.lock | ||
yarn.lock.readme.md |
README.md
Angular
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages.
Quickstart
Changelog
Learn about the latest improvements.
Want to help?
Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing and then check out one of our issues in the hotlist: community-help.