Based on the discussion in #776 we can't reliably check if a given
element has a particular property at the compilation time. As such
the existing algorithm detecting "missing" directives can't be used.
We need to see if there is a different / better algorithm or maybe
those checks need to be moved later in the process (runtime). Leaving
integration tests in place (disabled) so we can come back to the
topic after unblocking the situation.
This commit effectivelly reverts 94e203b9df
In view_container.js, templateElement.parentNode can be null
when two template tags are nested in one another.
Accessing the parent node through view.nodes[0].parentNode fixes
the problem.
closes#997Closes#999
Docs for the "Injecting a directive from the current element" indicate that having a dependency of `dependency: Dependency` should cause the current element's dependency to be injected, but then uses the ID value from the parent element in the example.
Closes#1032
so people using something like systemjs won't break the promise chain and at the same time shows that it's a promise
```es6
Promise.all({
app1: System.import('app1').then(module => module.main()),
app2: System.import('app2').then(module => module.main()),
app3: System.import('app3').then(module => module.main())
})
.then(function(injectors) {
console.log('dem injectors', injectors);
});
```
Closes#967
Ok I'm not sure (trying to understand angular2) but according to what i can see. Shouldn't the decorator event property be events. Please correct me if I'm wrong :p
Marc Laval
Pawel Kozlowski
Victor Berchet
David-Emmanuel Divernois
Matt Follett
Misko Hevery
Patrice Chalin
Tim Blasi
PatrickJS
Nick Van Dyck
vsavkin
Peter Bacon Darwin
Yegor Jbanov