angular.js/src/ngMock, branch v1.2.9 fix(ngMock): ensure ngAnimate isn't a required mock 2014-01-15T08:43:52+00:00 Matias Niemelä 2014-01-15T08:43:52+00:00 1413328e6aec87338bf1fce002dfaf519d9ca1b5 






feat($animate): use requestAnimationFrame instead of a timeout to issue a reflow
2014-01-14T18:21:19+00:00

Matias Niemelä

2014-01-12T20:49:52+00:00

4ae3184c5915aac9aa00889aa2153c8e84c14966

Closes #4278
Closes #4225





Closes #4278
Closes #4225







fix(ngMock window.inject): Remove Error 'stack' property changes
2014-01-07T01:47:06+00:00

Andrew C. Greenberg

2013-11-20T06:53:33+00:00

7e916455b36dc9ca4d4afc1e44cade90006d00e3

Recent browsers, particularly PhantomJS 1.9.2 and Safari 7.0
treat the stack property as non-configurable and unwritable.

Because window.inject captures the stack at the time of the inject,
and attempts to insert it into a captured throw from the injected
function by modifying e.stack, a meaningless error message and
stack is thrown instead.

This commit inserts two tests exposing the problem, and implements
a proposed solution that builds a new error-like object that mimicks
the old Error object, but with the additional stack information, and
captures the toString function from the Error object prototype.  This
appears to work for the browsers suppoerted here.




Recent browsers, particularly PhantomJS 1.9.2 and Safari 7.0
treat the stack property as non-configurable and unwritable.

Because window.inject captures the stack at the time of the inject,
and attempts to insert it into a captured throw from the injected
function by modifying e.stack, a meaningless error message and
stack is thrown instead.

This commit inserts two tests exposing the problem, and implements
a proposed solution that builds a new error-like object that mimicks
the old Error object, but with the additional stack information, and
captures the toString function from the Error object prototype.  This
appears to work for the browsers suppoerted here.






fix($httpBackend): use ActiveX XHR when making PATCH requests on IE8
2014-01-03T06:04:32+00:00

Igor Minar

2013-12-13T09:49:37+00:00

6c17d02bc4cc02f478775d62e1f9f77da9da82ad

IE8's native XHR doesn't support PATCH requests, but the ActiveX one does.

I'm also removing the noxhr error doc because nobody will ever get that error.

Closes #2518
Closes #5043





IE8's native XHR doesn't support PATCH requests, but the ActiveX one does.

I'm also removing the noxhr error doc because nobody will ever get that error.

Closes #2518
Closes #5043







fix(angular-mocks): use copy of mock data in $httpBackend
2013-12-11T23:18:45+00:00

Karl Seamon

2013-12-06T19:35:34+00:00

f69dc16241c8b631123ad0b09674f0a5e0ff32fe

Copy mock data returned from the mock $httpBackend.
This prevents modifications to the response from affecting future responses.
Previously, this misbehavior was being mitigated by the deep copy in $resource, but that no longer exists.





Copy mock data returned from the mock $httpBackend.
This prevents modifications to the response from affecting future responses.
Previously, this misbehavior was being mitigated by the deep copy in $resource, but that no longer exists.







chore(mocks): wrap angular-mocks.js in closure
2013-11-26T13:22:29+00:00

David Mosher

2013-11-22T00:50:23+00:00

5bd6596856c9f88c0ce3d96ff1ed4daa082cbe29

Closes #5080





Closes #5080







fix(ngMock): fixes httpBackend expectation with body object
2013-11-22T06:57:15+00:00

Corey Burrows

2013-11-14T14:42:35+00:00

4d16472b918a3482942d76f1e273a5aa01f65e83

Fixes an issue with httpBackend expectations where a given body object
may not match the actual request body if its keys are serialized in a
different order.

Closes #4956





Fixes an issue with httpBackend expectations where a given body object
may not match the actual request body if its keys are serialized in a
different order.

Closes #4956







chore(mocks): Remove reference to flushNext
2013-11-14T16:07:36+00:00

James deBoer

2013-11-12T01:25:57+00:00

04492ef2279e2be18162bef89b0a75992a400cae

Closes #4885





Closes #4885







fix(ngMock): throw more descriptive errors for $animate.flushNext()
2013-11-06T08:14:11+00:00

Jeff Cross

2013-11-06T07:30:48+00:00

6fb191570ee72f087e8bb6b1d8f5eea0f585886c












fix(angular-mocks): add inline dependency annotation
2013-10-28T19:45:00+00:00

Derek Hammer

2013-10-16T00:16:01+00:00

6d23591c31f2b41097ceaa380af09998e4a62f09

Annotation allows the angular-mocks to be minified, which sometimes happens with frameworks that
automatically process files before running tests.
Also, some developers have been using this library in code for their applications.
This is not recommended as the library is only designed to support testing and not production
applications.  If you are likely to want to use the code here in production you would be best
forking and maintaining your own version of the code as we will not guarantee that we won't
break the annotation of the code in the future.

Closes #4448





Annotation allows the angular-mocks to be minified, which sometimes happens with frameworks that
automatically process files before running tests.
Also, some developers have been using this library in code for their applications.
This is not recommended as the library is only designed to support testing and not production
applications.  If you are likely to want to use the code here in production you would be best
forking and maintaining your own version of the code as we will not guarantee that we won't
break the annotation of the code in the future.

Closes #4448