Question

22

How to pass extra data down a Parse Promise chain

rated 0 times [ 23] [ 1] / answers: 1 / hits: 15438 / 10 Years ago, tue, august 12, 2014, 12:00:00

In my Parse Cloude code I need to run a few successive queries, each of them using a find().

Example:

var promise = firstQuery.get(objectId).then(function(result1){

            return secondQuery.find();

        }).then(function(result2){

            return thirdQuery.find();

        }).then(function(result3) {



             // here I want to use result1, result2 and result3

        });

The question is: how do I access result1 and result2 in the final then statement, without assigning them to variables declared in the parent scope.

Why do I ask this: You cannot use the parent scope trick if you are nesting a bunch of promises which you create in a loop in order for them to be executed in parallel (imagine a for loop around the above statement whereby all the promises are put in an array and then evaluated using Parse.Promise.when. They would all start modifying the parent scope variables at the same time.)

Can I create some kind of promise object where I could return something along the lines of:

Parse.promise({result:result1,findResult:secondQuery.find()};

so I could get the values out of the result2 parameter by doing

result2.result

and

result2.findResult

I hope I make myself clear. This is not very easy to explain.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

anabeldaliad

Add To Favorites

Follow

Total Points: 552

Total Questions: 107

Total Answers: 120

Location: Hungary

Member since Mon, Feb 21, 2022

2 Years ago

answered 10 Years ago mckaylab · Accepted Answer

You can make use of closures to do this, without the need for any extra objects or wrapping.

var promise = firstQuery.get(objectId).then(function(result1){

    return secondQuery.find()

    .then(function(result2) {

        return thirdQuery.find()

        .then(function(result3) {

            //can use result1, result2, result3 here

        });

    });

});

This nested syntax is identical in function to your chaining syntax.

EDIT based on comments

If your promise chain is long and complex enough that this nested syntax becomes ungainly, the logic is probably complex enough to merit abstraction into its own function.

function complexQuery(objectId) {

    var results = {};

    return firstQuery.get(objectId).then(function(result1) {

        results.result1 = result1;

        return secondQuery.find();

    })

    .then(function(result2) {

        results.result2 = result2;

        return thirdQuery.find();

    })

    .then(function(result3) {

        results.result3 = result3;

        return results;

    });

}



complexQuery(objectId)

.then(function (results) {

    //can use results.result1, results.result2, results.result3

});

Personally, I think that's easier to read and maintain than messing around with .bind.