Miško Hevery 8a5eb08672 fix(fakeAsync): have fakeAsync use Proxy zone. (#10797) ... Closes #10503 It is possible for code in `beforeEach` to capture and fork a zone (for example creating `NgZone` in `beforeEach`). Subsequently the code in `it` may chose to do `fakeAsync`. The issue is that because the code in `it` can use `NgZone` from the `beforeEach`. it effectively can escape the `fakeAsync` zone. A solution is to run all of the test in `ProxyZone` which allows a test to dynamically replace the rules at any time. This allows the `beforeEach` to fork a zone, and then `it` to retroactively became `fakeAsync` zone.		2016-08-19 12:10:53 -07:00
..
src	fix(ngc): don't codegen foo.d.ngfactory.ts from foo.d.ts (#10833)	2016-08-18 10:11:06 -07:00
test	fix(fakeAsync): have fakeAsync use Proxy zone. (#10797)	2016-08-19 12:10:53 -07:00
tsconfig.json	fix(ngc): Revert "fix(ngc): add an option to produce TS1.9-pathMapping imports (#10602)" (#10765)	2016-08-12 17:38:29 -07:00