This is possible, and even quite easy! Well, if we look at how Angular’s own promises work, we need to get Bluebird to $evalAsync somewhere in order to get the exact same behavior. If we do that, the fact both implementations are Promises/A+ compliant means we can interop between $q code and Bluebird code, meaning … Read more
What you need to use is $q.all which combines a number of promises into one which is only resolved when all the promises are resolved. In your case you could do something like: function outerFunction() { var defer = $q.defer(); var promises = []; function lastTask(){ writeSome(‘finish’).then( function(){ defer.resolve(); }); } angular.forEach( $scope.testArray, function(value){ promises.push(writeSome(value)); … Read more
I want the all to resolve when all the chains have been resolved. Sure, then just pass the promise of each chain into the all() instead of the initial promises: $q.all([one.promise, two.promise, three.promise]).then(function() { console.log(“ALL INITIAL PROMISES RESOLVED”); }); var onechain = one.promise.then(success).then(success), twochain = two.promise.then(success), threechain = three.promise.then(success).then(success).then(success); $q.all([onechain, twochain, threechain]).then(function() { console.log(“ALL PROMISES … Read more
But if I want to use $scope.tempObject after callback so how can I use it. ? You need to chain from the httpPromise. Save the httpPromise and return the value to the onFullfilled handler function. //save httpPromise for chaining var httpPromise = $http({ method: ‘GET’, url: ‘/myRestUrl’ }).then(function onFulfilledHandler(response) { $scope.tempObject = response console.log(“Temp Object … Read more
Well, I’m assuming you don’t keep an explicit reference to it since that would force it to stay allocated. The simplest test I could think of is actually allocating a lot of promises and not resolving them: var $q = angular.injector([“ng”]).get(“$q”); setInterval(function () { for (var i = 0; i < 100; i++) { var … Read more
Is this the right approach? Yes. The use of memoisation on functions that return promises a common technique to avoid the repeated execution of asynchronous (and usually expensive) tasks. The promise makes the caching easy because one does not need to distinguish between ongoing and finished operations, they’re both represented as (the same) promise for … Read more
You are asking how to chain functions in promises. 3) How can I transfer data between them? 4) How can I make the following function depend on its previous result? Return data (or a promise) for the next function in the chain: var p2 = p1.then ( function (data) { var nextData = someFn(data); return … Read more
This feature was added to the 1.1.5 release via a timeout parameter: var canceler = $q.defer(); $http.get(‘/someUrl’, {timeout: canceler.promise}).success(successCallback); // later… canceler.resolve(); // Aborts the $http request if it isn’t finished.
You should change it to var getTokens = function() { return $http.get(‘/api/tokens’); }; And, then in other module use yourModule.getTokens() .then(function(response) { // handle it }); As to why it’s an anti-pattern, I’d say that, first, it doesn’t allow you to further chain your success/fail handler methods. Second, it handles the control of processing the … Read more
Have you had a look at $routeProvider.when(‘/path’,{ resolve:{…}? It can make the promise approach a bit cleaner: Expose a promise in your service: app.service(‘MyService’, function($http) { var myData = null; var promise = $http.get(‘data.json’).success(function (data) { myData = data; }); return { promise:promise, setData: function (data) { myData = data; }, doStuff: function () { … Read more