From 561186a075a1c5125959285e8c638a2e1c46364b Mon Sep 17 00:00:00 2001 From: Christoph Burgdorf Date: Thu, 19 Dec 2013 20:48:43 +0100 Subject: [PATCH] docs($http): remove outdated part about $http outside of $apply phase This removes some outdated advice which no longer is true against the latest angular version. Relates to #5206 --- src/ng/http.js | 29 +---------------------------- 1 file changed, 1 insertion(+), 28 deletions(-) diff --git a/src/ng/http.js b/src/ng/http.js index e7bbb8bc6e93..1f8586cca437 100644 --- a/src/ng/http.js +++ b/src/ng/http.js @@ -223,34 +223,7 @@ function $HttpProvider() { * XMLHttpRequest will transparently follow it, meaning that the error callback will not be * called for such responses. * - * # Calling $http from outside AngularJS - * The `$http` service will not actually send the request until the next `$digest()` is - * executed. Normally this is not an issue, since almost all the time your call to `$http` will - * be from within a `$apply()` block. - * If you are calling `$http` from outside Angular, then you should wrap it in a call to - * `$apply` to cause a $digest to occur and also to handle errors in the block correctly. - * - * ``` - * $scope.$apply(function() { - * $http(...); - * }); - * ``` - * - * # Writing Unit Tests that use $http - * When unit testing you are mostly responsible for scheduling the `$digest` cycle. If you do - * not trigger a `$digest` before calling `$httpBackend.flush()` then the request will not have - * been made and `$httpBackend.expect(...)` expectations will fail. The solution is to run the - * code that calls the `$http()` method inside a $apply block as explained in the previous - * section. - * - * ``` - * $httpBackend.expectGET(...); - * $scope.$apply(function() { - * $http.get(...); - * }); - * $httpBackend.flush(); - * ``` - * + * * # Shortcut methods * * Since all invocations of the $http service require passing in an HTTP method and URL, and