This adds a unit test to the transpiler. Existing tests are themselves transpiled to ES5, which makes it impossible to do some kinds of assertions. For example, this will be useful to repro https://github.com/angular/angular/issues/509.
In this change, the actual issue isn't fixed. It only adds the reproduction.
It uses the jasmine test runner, since it's already used by the docs test. That uses version 1 of Jasmine, which isn't ideal, but I want to be consistent for now.
I discussed with Tobias the possibility of switching to Mocha for these nodejs-based tests, and we might do that sometime later.
Export files are now directly under the module folder,
e.g. `core/core.js`. With this, an import like `core/core`
won’t need a path mapping (e.g. via `System.paths`) any more.
This adds the `src` folder to all other import statements as well.
Old syntax:
- ng-repeat: #item in items;
- ng-repeat: #item; in: items;
- <template let-ng-repeat=“item” [in]=items>
New syntax:
- ng-repeat: var item in items;
- ng-repeat: var item; in items
- <template ng-repeat var-item [in]=items>
Notice that the var is now a standalone binding
rather then an argument to ng-repeat. This will
make the var bindings consistent with the rest of
the system.
Closes#482
npm install yields a warning
```bash
npm WARN package.json angular@0.0.0 No repository field.
```
also include `"bugs": "https://github.com/angular/angular/issues"`
modules/angular has no implementation, but depends on all the pieces
that make angular - core, di, directives, etc. It is the package that
all client apps will depend on.
There are lots of issues being created regarding the 1.3 version in this repo.
Warning the users that this repo is for Angular 2.0 should avoid this confusion.
Closes#373
Yegor Jbanov
Pawel Kozlowski
vsavkin
Alex Eagle
Bertrand Laporte
Brian Ford
Kevin Moore
Tobias Bosch
Misko Hevery
Marc Laval
gdi2290
Victor Berchet
otodockal
Rado Kirov
Ciro Nunes