angular-cn/packages/core
Tobias Bosch 2c5a671341 fix: don't instantiate providers with ngOnDestroy eagerly. (#15070)
BREAKING CHANGE:

Perviously, any provider that had an ngOnDestroy lifecycle hook would be created eagerly.

Now, only classes that are annotated with @Component, @Directive, @Pipe, @NgModule are eager. Providers only become eager if they are either directly or transitively injected into one of the above.

This also makes all `useValue` providers eager, which
should have no observable impact other than code size.

EXPECTED IMPACT:
Making providers eager was an incorrect behavior and never documented.
Also, providers that are used by a directive / pipe / ngModule stay eager.
So the impact should be rather small.

Fixes #14552
2017-03-14 14:32:26 -07:00
..
src fix: don't instantiate providers with ngOnDestroy eagerly. (#15070) 2017-03-14 14:32:26 -07:00
test fix: don't instantiate providers with ngOnDestroy eagerly. (#15070) 2017-03-14 14:32:26 -07:00
testing fix: don't instantiate providers with ngOnDestroy eagerly. (#15070) 2017-03-14 14:32:26 -07:00
index.ts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
package.json refactor: More generic build.sh file 2017-03-08 16:29:28 -08:00
public_api.ts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
rollup.config.js build: fix file paths after moving modules/@angular/* to packages/* 2017-03-08 16:29:28 -08:00
tsconfig-build.json refactor: More generic build.sh file 2017-03-08 16:29:28 -08:00