d6791ff0e0
This commit introduces a new API to the ngUpgrade module, which is compatible with AoT compilation. Primarily, it removes the dependency on reflection over the Angular 2 metadata by introducing an API where this information is explicitly defined, in the source code, in a way that is not lost through AoT compilation. This commit is a collaboration between @mhevery (who provided the original design of the API); @gkalpak & @petebacondarwin (who implemented the API and migrated the specs from the original ngUpgrade tests) and @alexeagle (who provided input and review). This commit is an starting point, there is still work to be done: * add more documentation * validate the API via internal projects * align the ngUpgrade compilation of A1 directives closer to the real A1 compiler * add more unit tests * consider support for async `templateUrl` A1 upgraded components Closes #12239 |
||
---|---|---|
.github | ||
docs | ||
modules | ||
scripts | ||
tools | ||
.bowerrc | ||
.clang-format | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.nvmrc | ||
.travis.yml | ||
CHANGELOG.md | ||
COMMITTER.md | ||
CONTRIBUTING.md | ||
DEVELOPER.md | ||
LICENSE | ||
NAMING.md | ||
README.md | ||
SAVED_REPLIES.md | ||
TOOLS.md | ||
TRIAGE_AND_LABELS.md | ||
bower.json | ||
browser-providers.conf.js | ||
build.sh | ||
circle.yml | ||
gulpfile.js | ||
karma-js.conf.js | ||
npm-shrinkwrap.clean.json | ||
npm-shrinkwrap.json | ||
npm-shrinkwrap.readme.md | ||
package.json | ||
protractor-e2e.conf.js | ||
protractor-examples-e2e.conf.js | ||
protractor-perf.conf.js | ||
publish-packages.sh | ||
shims_for_IE.js | ||
test-main.js | ||
test.sh | ||
tslint.json |
README.md
Safari (7+), iOS (7+), Edge (14) and IE mobile (11) are tested on BrowserStack.
Angular
Angular is a development platform for building mobile and desktop web applications. This is the repository for Angular 2 Typescript/JavaScript (JS).
Angular2 for Dart can be found at dart-lang/angular2.
Quickstart
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.