{"push_id":1201849010,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"267ee9c892b0eb40908700ee2435793f8c6c1c84","before":"859b1e300cfc09a9d0740e6ac028665ad96c93fd","commits":[{"sha":"267ee9c892b0eb40908700ee2435793f8c6c1c84","author":{"name":"Kate Miháliková","email":"0f5dee8a4155160232337cb90ee34fa23238ecce@gmail.com"},"message":"fix(ngMock): trigger digest in `$httpBackend.verifyNoOutstandingRequest()`\n\nFiring a digest at the beginning of the verification process, ensures that requests fired\nasynchronously - e.g. in the `resolve` handler of a promise as happens with `$http` - will get\ndetected as well.\nPreviously, in order to reliably verify that there was no outstanding request, users needed to\nmanually trigger a digest, before calling `verifyNoOutstandingRequest()`. Failing to do so, could\nprevent `verifyNoOutstandingRequest()` from detecting pending requests and cover bugs in application\ncode.\nThis is no longer the case, since a digest will always be fired autommatically as part of a call to\n`verifyNoOutstandingRequest()`.\n\nFixes #13506\nCloses #13513\n\nBREAKING CHANGE:\n\nCalling `$httpBackend.verifyNoOutstandingRequest()` will trigger a digest. This will ensure that\nrequests fired asynchronously will also be detected (without the need to manually trigger a digest).\nThis is not expected to affect the majority of test-suites. Most of the time, a digest is (directly\nor indirectly) triggered anyway, before calling `verifyNoOutstandingRequest()`.\nIn the unlikely case that a test needs to verify the timing of a request with respect to the digest\ncycle, you should rely on other means, such as mocking and/or spying.","distinct":true,"url":"https://api.github.com/repos/angular/angular.js/commits/267ee9c892b0eb40908700ee2435793f8c6c1c84"}]}
{"actor":{"display_login":"gkalpak"}}