angular-cn

Commit Graph

Author	SHA1	Message	Date
Kara	2b313e4979	feat(forms): add support for disabled controls (#10994 )	2016-08-24 16:58:43 -07:00
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
Kara	7f6685e451	test(forms): refactor form model tests to three files (#10774 )	2016-08-13 17:26:08 -07:00

Author

SHA1

Message

Date

Kara

2b313e4979

feat(forms): add support for disabled controls (#10994 )

2016-08-24 16:58:43 -07:00

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

Kara

7f6685e451

test(forms): refactor form model tests to three files (#10774 )

2016-08-13 17:26:08 -07:00

3 Commits