Still need waitFor? about refluxjs

[spoike]

I still struggle with finding a motivating example for this functionality. I haven't run into this problem yet when dog fooding Reflux in my own project because the work around is to let lower-level store listen to other stores which turns out to be a much simpler solution. The lower-level store can get the raw action data (from e.g. ajax calls) if the higher-level store makes it accessible.

From my P.O.V. this seems to be a design consideration for the user's application rather than Reflux itself.

I'm open to suggestions with motivating examples from the community, so I know why this needs to be implemented.

[dashed]

I think something like waitFor is out of scope for this project and promises does this sort of thing well:

var Promise = require("bluebird");

var waitFor = function() {

    var last = arguments.length - 1,
        promises = [];

    for (var i = 0; i < last; ++i) {

        var listenable = arguments[i];

        var promise = new Promise(function(fulfill){
            listenable.listen(fulfill);
        });

        promises.push(promise);

    }

    promises.push(arguments[last]);

    Promise.join.apply(null, promises);

};

// Creates a DataStore
var statusStore = Reflux.createStore({

    // Initial setup
    init: function() {

        waitFor(action, store, anotherStore, anotherAction, this.output);
    },

    // Callback
    output: function(flag) {
        var status = flag ? 'ONLINE' : 'OFFLINE';

        // Pass on to listeners
        this.trigger(status);
    }

});

[KyleAMathews]

Very nice! I agree @spoike that generally speaking waitFor isn't needed and since @dashed was kind enough to contribute an easy promise-based solution, I'll close this.