We can call a $scope.

As specified https://docs.angularjs.org/api/ngResource/service/%24resource request can be cancelled by means of a function $cancelRequest♪ To this end, an option should be added to the method cancellable♪This parameter works for the version, starting with 1.5.0♪Example https://jsfiddle.net/Stepan_Kasyanenko/9dcdqx68/ ♪angular.module('ExampleApp', ['ngResource']) .controller('ExampleController', function(ExampleService) { var vm = this; //Массив для отображения информации о запросах vm.request = []; vm.start = function() { vm.cancel(); //Отменяем предыдущий запрос ExampleService.getData(1).$promise .then(function() { console.log('success'); }) .catch(function(data) { console.log('catch', data); vm.request.push(data); }); }; vm.cancel = function() { if (ExampleService.getData.$promise) ExampleService.getData.$promise.$cancelRequest(); }; }) .service('ExampleService', function($resource) { var Example = $resource("/data/:id", { id: "@id" }, { // Let's make the `query()` method cancellable query: { method: 'get', isArray: true, cancellable: true } }); return { getData: function(id) { // Сохраняем промис для отмены this.getData.$promise = Example.query({ id: id }); return this.getData.$promise; } } });<script src="https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.5.8/angular.js"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.5.8/angular-resource.js"></script> <div ng-app="ExampleApp"> <div ng-controller="ExampleController as vm"> <button ng-click="vm.start()"> Start Request </button> <button ng-click="vm.cancel()"> Cancel Request </button> <div ng-repeat="req in vm.request"> <pre>{{$index}}: status = {{req.status}} statusText = {{req.status==-1?"Cancelled":req.statusText}}</pre> </div> </div> </div>Unfortunately, the snipe doesn't work. But the code is working and jsfiddle, too.

Like this:var records = []; function getItems(deferred) { deferred = deferred || $q.defer(); promiseLoadData(gid, data).then(function (response) { Array.prototype.push.apply(records, response.data); //Добавляем наши записи в массив if (response.data.length == 100) getItems(deferred); //Если количество записей равно 100 - получаем следующую порцию. else { //Получена последняя порция записей deferred.resolve(); } }, deferred.reject); return deferred.promise; } getItems().then(function () { console.log('все записи успешно получены. Всего записей', records.length); }, function () { //При получннии записей произошла ошибка });

In the code, there are two major problems (out of three) starting javascript developers, I see.Problem one is not understanding asynchronicity.Of course, the cycle is not expecting a return to the asynchronous operation in order to move on. Imagine that you have four hyperactive butlers, and you're throwing them four balls. How are they gonna bring them back? Damn it.And what's inside Promise.then, it's colbec, just written more comfortable.What do we do?Don't:The first solution that comes to mind, and let's wait for the end of the first operation, and then the cycle meter will increase and start the next operation in the next iteration. But you're just turning the asynchronous operation into synchronous and losing all your asynchronic prophysics.We should:To understand that the main problem of this code is not asynchronous, but that you don't understand the circuit. I mean, you're not embarrassed that you're having a consult. json/1_1_1.json So many times? Problem two:ignorance of the areas of visibility in js, they're flooding. The question of the loss of the variable in the cycle is top 1, at interviews with the developer &apos; s Middle, when the conversation is not answerable. On this resource, this issue is dealt with in different language several times a week. For example https://ru.stackoverflow.com/questions/486204/%D0%9F%D1%80%D0%B8%D0%BD%D1%86%D0%B8%D0%BF-%D1%80%D0%B0%D0%B1%D0%BE%D1%82%D1%8B-%D0%B2%D0%BB%D0%BE%D0%B6%D0%B5%D0%BD%D0%BD%D1%8B%D1%85-%D1%84%D1%83%D0%BD%D0%BA%D1%86%D0%B8%D0%B9-%D0%B8%D0%BB%D0%B8-%D0%BD%D0%B5%D0%BF%D0%BE%D0%BD%D1%8F%D1%82%D0%BD%D0%BE%D0%B5-%D0%B7%D0%B0%D0%BC%D1%8B%D0%BA%D0%B0%D0%BD%D0%B8%D0%B5-%D0%B2-javascript (not mentioning a block of scope in es6 true).I mean, the core of your code is like, for(var i = 0; i<4; i++){ setTimeout(function(){console.log(i)}, 1000) } setTimeout It's like a simple asynchronous operation. If you don't understand why it'll be four times four, you'll have to meditate until you understand. I will.In brief, this is because the scoop in js for var variables is a function, not a figure box. The cycle of a separate scoop does not form and will all four times refer to the same variable i, the same area of memory.Okay, I get it, I still want it synchronized.In order to control the management of multiple asynchronous requests, there are a number of common libraries, such as http://caolan.github.io/async/ Look at this. async.waterfall

800,000 pages probably won't have to be scratched. As soon as you've been searched by a page that, in the framework of the four investments, refers to the end page, the search stops and (through from #1 to #2) = true;

If you want to use it Promises (Promise), first, you need to modify your functions so that they return. Promises♪ For example, the first of your functions will be:function f1() { return new Promise(function(resolve){ setTimeout(function() { console.log(1); resolve(); }, 30); }); } The remaining functions are similarly transformed.Now you have three functions.f1♪ f2♪ f3which return Promises And you want to keep them in line. If you don't use libraries like Bluebird, you're going to have to implement the call line. Promises manually. It's not as complicated as it seems:// Аргумент "deeds" - это массив функций, которые должны выполняться // последовательно. При этом, каждая функция должна возвращать // Обещание (Promise). var seqRunner = function(deeds) { return deeds.reduce(function(p, deed) { return p.then(function() { // Выполняем следующую функцию только после того, как отработала // предыдущая. return deed(); }); }, Promise.resolve()); // Инициализируем очередь выполнения. } And you need to use this line like this:seqRunner([f1, f2, f3]).then(function() { console.log('Done!'); }); Here comes JSFiddle with https://jsfiddle.net/we0y2hg2/1/ ♪Comment:If you've got a pre-recognition, a small number of functions, you might as well have no function. seqRunner and seize functions manually:f1().then(function() { return f2(); }).then(function() { return f3(); }).then(function() { console.log('Done!'); });

Set up a series of timer events1. What a mistake.In your code, function a() Establish a timer based on the value derived from the function b()♪ But... b() It doesn't come back because it's a line. return 2000; inside the function function()which causes the timer. Because of that. a() Trying to put his timer on. undefined and team console.log(3); I'm doing it right now, without the pussy.2. If the timers are set, starting with the firstWe'll start the next timer after the last one's working.Your code may be:a(); function a() { console.log(1); setTimeout(function() { b(); }, 5000 ); } function b() { console.log(2); setTimeout(function() { c(); }, 2000 ); } function c() { console.log(3); }In general, it is possible to: var delays = [ 5000, 4000, 3000, 2000 ]; delayConsole(0); function delayConsole( i ) { if( i < delays.length ) { console.log( (i+1) + '. ' + delays[i] ); setTimeout(function() { delayConsole( i+1 ) }, delays[i] ); } else { console.log( 'the end' ); }; }3. If timers are installed, starting with the lastAll timers are running straight. In order to start another timer, the function adds to all the delays before it. Your code may be:a(); function a() { setTimeout(function() { console.log(3); }, 2000 + b() ); } function b() { var delayB = 5000; setTimeout(function() { console.log(2); }, delayB + c() ); return delayB; } function c() { console.log(1); return 0; }In general, it is possible to:var delays = [ 5000, 4000, 3000, 2000 ]; delayConsoleBackward( delays.length ); function delayConsoleBackward( i ) { if( i > 0 ) { var sumDelay = delayConsoleBackward( i-1 ) + delays[i-1]; setTimeout(function() { console.log( ( i < delays.length ? i+1 : 'the end' ) + ' is after ' + sumDelay ); }, sumDelay); return sumDelay; } else { console.log( 1 ); return 0; }; }

You can choose the necessary fields and wait for them to be carried out together with help. https://developer.mozilla.org/ru/docs/Web/JavaScript/Reference/Global_Objects/Promise/all (if one of the elements of the mass is not Promiseit will be automatically converted into it by Promise.resolvefetch('http://some-site.com/cors-enabled/some.json', {mode: 'cors'}) .then(function(response) { return Promise.all([response.text(), /*что-то еще*/, /* что-то еще*/]); }) .then(function(array) { var text = array[0]; var /*что-то еще*/ = array[1]; var /* что-то еще*/ = array[2]; console.log('Request successful', text); }) .catch(function(error) { log('Request failed', error) }); Either it's easier to do, to keep the necessary promise, and to respond already.var fetchResult = fetch('http://some-site.com/cors-enabled/some.json', {mode: 'cors'}); fetchResult.then(function(response) { return response.text(); }).then(function(text) { console.log('Request successful', text); }); fetchResult.then(function(response) { return response.json(); }).then(function(json) { console.log('Request successful', json); });

Why is this difference in the form of withdrawal between response.data and promise?Because objects are different types, response.data - The processed result of the request, and promise is an object that can be in several states and has no connection to the request. It makes sense that they have different conclusions.How to correctly assign the variable result of the request so that the elements of the facility can be treated in a manner such as:$scope.getProfileData.id etc.It doesn't, because it's asynchronous. Only in the processor then for a successful or erroneous promise.Depending on the task, the solution may be different, starting from the fact that you don't need to use the value outside the control room. thenand end of use ngResource which passes right in view or expects to move to resolve status at the state change stage or route

In general terms, the asynchronous cycle on js is conducted through the course:function foo() { return какойтаАсинхронныйВызов() .then(function(result) { if (какие-то условие) return foo() else return result; }) } It is not necessary to make such a challenge in a separate service - a sufficient asynchronous function.By the way, I wouldn't recommend that. errorCallback for each challenge then If you just need to show the message to the user, it's enough to process the mistake just once, at the end.If the challenge is to swallow a mistake (and to go to the other end of the cycle) it is not necessary to show the message to the user:function foo() { return какойтаАсинхронныйВызов() .then(function(result) { if (какие-то условие) return foo() else return result; }, function() { return foo() }) } PS Summary responseRecurring seems to be working, but how do you return promise?Through return♪

The problem isn't exactly where you put it on your question. The resulting list (and work with it) needs to be obtained after all has been completed. db.Widget.findOne().then()♪ You need to. https://learn.javascript.ru/promise#promise-all-iterable var ind = 0, widgets_list = [], promises = []; for (ind = 0; ind < data.widgetsID.length; ind++) { promises.push(db.Widget.findOne({'_id': data.widgetsID[ind]}).then(function(widget) { if(widget) { widgets_list.push(widget); } })); } Promise.all(promises).then(function() { // что-нибудь делаем с widgets_list })

Since the question is "how to translate," not "how to use" terms, you can meet such translation variants:promise - promise Example, we're here. Promise To do something when it comes to this kind of event, it sounds much better for a Russian-speaking man than, "We're building. promise To fulfil...Since it's about terminology, it's probably instead of words. future (The present, the future) meant the word feature♪feature - has several translation options: features, characteristics, characteristics, function, means, etc., which can be used differently depending on context.Examples: key features - basic (key) characteristics; feature logic - logic of signs.

If you don't pay attention to the other weirdness of the code, you obviously do. return Not where you want. But that code still doesn't work, you have to understand that Promise returns the answer asynchronously and transfers it to the collback. .then()and in your case inside filter It'll always be true, since the revolving object Promise exists. For example, http://bluebirdjs.com/docs/api/promise.filter.html , looks like in your case this is what you need to replace. filter underscore.

function b The Promise can be returned if you add return, so there is no need to create it. afunction a(){ var info = {email: 'email@email.ru'}, user = b(info); user.then(function(result) { res.send( result ); }); } function b(params){ return model.user.findAll({ where:{ email: params['email'] } }).then(function(user){ return(user); }); }

Write this thing "with promises" like this:_openMenu(target) { new Promise((resolve) => { this._closeMenu(); target.classList.add('isActive'); target.nextElementSibling.classList.add('isOpened'); setTimeout(resolve, 0); }) .then(() => { document.addEventListener('click', this._closeMenu); }); } or so:_openMenu(target) { this._closeMenu(); target.classList.add('isActive'); target.nextElementSibling.classList.add('isOpened'); new Promise((resolve) =&gt; setTimeout(resolve, 0)) .then(() =&gt; document.addEventListener('click', this._closeMenu)); } But I wouldn't call any of those options right. Because there's no need for promises in this task.The area of application of the promises is the reversal of the values from the function. For example, a function that illustrates the modular dialogue could return the promise containing the value added by the user in the dialogue.

Promise keeps it. You can't use the same promise without rebuilding it.

You don't use it. reject - he's doing exactly what you need.And to make a mistake, but to leave it wrong, you have to use it. return Promise.reject(...) or throw ... in the processor:new Promise(function(_, reject) { reject(); }) .then(function() { console("ok") }, function() { console.log("rejected"); return Promise.reject(); }) .then(function() { console("ok") }) .then(function() { console("ok") }, function() { console.log("rejected"); return Promise.reject(); }) // вывод: // rejected // rejected

I don't know much about your project, but let's say there's an asynchronous function. meeedlennnno()which takes a lot of time, say, 30 seconds to figure something out.Now there's a big problem: the whole code is in the same process, so if it's a cause. meeedlennnno(), the calculation begins, and at the same time the user will send a request to your server, he will have to wait at least thirty seconds.This is not dependent on the use of promises. Nothing magical promises, promises just like https://ru.wikipedia.org/wiki/%D0%A1%D0%B8%D0%BD%D1%82%D0%B0%D0%BA%D1%81%D0%B8%D1%87%D0%B5%D1%81%D0%BA%D0%B8%D0%B9_%D1%81%D0%B0%D1%85%D0%B0%D1%80 for callback's. The function is asynchronous, but it is in the same process with all the others.There's a problem in the browser and Node.js. How do you decide? The browser uses the Web Workers and Node.js will be launched https://nodejs.org/api/child_process.html ♪

// Get options var categories = $http.get(PATH+'-categories', {cache: true}), formats = $http.get(PATH+'-formats', {cache: true}); $q.all([categories, formats]).then(function(response){ scope.categories = response[0].data; scope.formats = response[1].data; });

@Regent, took your clues and rewritten the manager. var _manager = function (i) { var deferred = $q.defer(); _doer(i) .then(function (data) { i++; console.log('isStop = ' + isStop, 'i = ' + i); if (data.state === 'ok' && !isStop && i < 7) { // доп. условие остановки //deferred.resolve({state: 'ok', i: i}); return _manager(i); } else { //deferred.resolve({state: 'end', i: data.i}); return {state: 'end', i: data.i}; } }, function (data) { //deferred.reject({state: 'error', i: data.i}); return {state: 'error', i: data.i}; }) .then(function (data) { if(data.state === 'ok') { deferred.resolve({state: 'ok', i: data.i}); } else if (data.state === 'end') { deferred.resolve({state: 'end', i: data.i}); } else { deferred.resolve({state: 'error', i: data.i}); } }) ; return deferred.promise; }; Now everything works as I need. But I think it might be shorter.