c61e4d7841
In View Engine, animation metadata could occur in nested arrays which would be flattened in the compiler. When compiling a component for Ivy however, the compiler no longer statically evaluates a component's animation metadata and is therefore unable to flatten it statically. This resulted in an issue to find animations at runtime, as the metadata was incorrectly registered with the animation engine. Although it would be possible to statically evaluate the animation metadata in ngtsc, doing so would prevent reusable animations exported from libraries from being usable as ngtsc's partial evaluator is unable to read values inside libraries. This is unlike ngc's usage of static symbols represented in a library's `.metadata.json`, which explains how the View Engine compiler is able to flatten the animation metadata statically. As an alternative solution, the metadata flattening is now done in the runtime during the registration of the animation metadata with the animation engine. Fixes #32794 PR Close #32818 |
||
|---|---|---|
| .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 | ||
| renovate.json | ||
| 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.