async.js each get index in iterator

后端 未结 6 1687
一整个雨季
一整个雨季 2021-02-02 07:04

I\'m using caolan\'s async.js library, specifically the .each method.

How do you get access to the index in the iterator?

async.each(ary, function(elemen         


        
相关标签:
6条回答
  • 2021-02-02 07:38
    1. indexOf solution is slow and should not be used for large arrays.
    2. eachSeries solution by Merc does't make what you want.
    3. Effective workaround is just to build another array with indexes:
    someArrayWithIndexes = someArray.map(function(e, i) {return {obj: e, index: i}});
    async.each(someArrayWithIndexes , function(item, done){
        console.log("Index:", item.index);
        console.log("Object:", item.obj);
    });
    
    0 讨论(0)
  • 2021-02-02 07:40

    modern-async's forEach() implementation is similar but gives you access to the index.

    0 讨论(0)
  • 2021-02-02 07:41

    Just use async.forEachOf().

    async.forEachOf(arr, function(value, index, callback) { ... }, ...
    

    For detail, see documentation here.

    0 讨论(0)
  • 2021-02-02 07:53

    The method async.each() will iterate the array in parallel, and it doesn't provide the element's index to the iterating callback.

    So when you have:

    function( done ){
    
      async.each(
    
        someArray,
    
        function( item, cb ){
          // ... processing
    
          cb( null );
        },
    
        function( err ){
          if( err ) return done( err );
    
          // ...
          done( null );
        }
      );
    }
    

    While you COULD use Array.indexOf() to find it:

    function( done ){
    
      async.each(
    
        someArray,
    
        function( item, cb ){
          // ... processing
    
          var index = someArray.indexOf( item );
    
          cb( null );
        },
    
        function( err ){
          if( err ) return done( err );
    
          // ...
          done( null );
        }
      );
    }
    

    This requires an in-memory search in the array for EVERY iteration of the array. For large-ish arrays, this might slow everything down quite badly.

    A better workaround could be by using async.eachSeries() instead, and keep track of the index yourself:

    function( done ){
    
      var index = -1;
      async.eachSeries(
    
        someArray,
    
        function( item, cb ){
    
          // index is updated. Its first value will be `0` as expected
          index++;
    
          // ... processing
    
          cb( null );
        },
    
        function( err ){
          if( err ) return done( err );
    
          // ...
          done( null );
        }
      );
    }
    

    With eachSeries(), you are guaranteed that things will be done in the right order.

    Another workaround, which is the async's maintainer's first choice, is to iterate with Object.keys:

    function( done ){
    
      async.each(
    
        Object.keys( someArray ),
    
        function( key, cb ){
    
          // Get the value from the key          
          var item = someArray[ key ];
    
          // ... processing
    
          cb( null );
        },
    
        function( err ){
          if( err ) return done( err );
    
          // ...
          done( null );
        }
      );
    }
    

    I hope this helps.

    0 讨论(0)
  • You can use async.forEachOf - it calls its iterator callback with the index as its second argument.

    > async.forEachOf(['a', 'b', 'c'], function () {console.log(arguments)});
    { '0': 'a', '1': 0, '2': [Function] }
    { '0': 'b', '1': 1, '2': [Function] }
    { '0': 'c', '1': 2, '2': [Function] }
    

    see the docs for more info.

    0 讨论(0)
  • 2021-02-02 07:57

    Update

    Since writing this answer, there is now a better solution. Please see xuanji's answer for details

    Original

    Thanks to @genexp for a simple and concise example in the comments below...

    async.each(someArray, function(item, done){
        console.log(someArray.indexOf(item));
    });
    

    Having read the docs, I suspected that there wasn't any way to access an integer representing position in the list...

    Applies an iterator function to each item in an array, in parallel. The iterator is called with an item from the list and a callback for when it has finished. If the iterator passes an error to this callback, the main callback for the each function is immediately called with the error.

    Note, that since this function applies the iterator to each item in parallel there is no guarantee that the iterator functions will complete in order.

    So I dug a little deeper (Source code link)

    async.each = function (arr, iterator, callback) {
            callback = callback || function () {};
            if (!arr.length) {
                return callback();
            }
            var completed = 0;
            _each(arr, function (x) {
                iterator(x, only_once(function (err) {
                    if (err) {
                        callback(err);
                        callback = function () {};
                    }
                    else {
                        completed += 1;
                        if (completed >= arr.length) {
                            callback(null);
                        }
                    }
                }));
            });
        };
    

    As you can see there's a completed count which is updated as each callback completes but no actual index position.

    Incidentally, there's no issue with race conditions on updating the completed counter as JavaScript is purely single-threaded under the covers.

    Edit: After digging further into the iterator, it looks like you might be able to reference an index variable thanks to closures...

    async.iterator = function (tasks) {
        var makeCallback = function (index) {
            var fn = function () {
                if (tasks.length) {
                    tasks[index].apply(null, arguments);
                }
                return fn.next();
            };
            fn.next = function () {
                return (index < tasks.length - 1) ? makeCallback(index + 1): null;
            };
            return fn;
        };
        return makeCallback(0);
    };
    
    0 讨论(0)
提交回复
热议问题