move-on is a module that:\r\n.all\r\n and\r\n \r\n .race\r\n methods [sample] [sample] [sample]this reference\r\n \r\n inner context\r\n for all functions in the chain to transmit data between functions [sample] [sample] [sample]Any bugs found? Give me to know on\r\n GitHub.
\r\nnpm install move-on\r\n Add the move-on.js library to the HTML file.
\r\n The library is located in ./dist/move-on.js directory.
\r\n It is a webpack&babel bundled cross-browser library version.
\r\n The library is accessible as moveOn variable in the global (window) scope.
\r\n\r\n```html\r\n\r\n\r\n```\r\n\r\n
npm test\r\n\r\n```cmd\r\n> git clone https://github.com/devrafalko/move-on.git\r\n> cd move-on\r\n> npm install\r\n> npm test //run tests in node\r\n> npm test err //run tests in node with failed specs shown\r\n> npm test deep //run tests in node with errors' descriptions shown\r\n```\r\n\r\nThe module's methods expect the [Array]\r\n\r\n list of functions to be passed as the first argument. Each function in the chain has the\r\n\r\n resolve\r\n and\r\n\r\n reject\r\n parameter, that should be called when ready\r\n(or failed) in order to move the functions execution forward. When the functions chain is successfully executed, the\r\n\r\n done\r\n callback function is called finally, otherwise the\r\n\r\n catch\r\n callback function is called.
moveOn\r\nThe chained functions are executed sequentially\r\n(one after another). Each function is expected to be\r\n\r\n resolved\r\n, so that the next chained function was executed. The\r\n\r\n done\r\n function is called as the last one, when all previous chained functions resolved. The\r\n\r\n catch\r\n function is called instead of\r\n\r\n done\r\n function, when at least one chained function failed\r\n(rejected).
\r\nSee the full description below.
See the samples: [sample] [sample] [sample] [sample] [sample] [sample] [sample]
moveOn.all\r\nThe\r\nall static method of\r\nmove-on module executes all chosen functions at the same time\r\n(similarly to Promises'\r\n \r\n .all\r\n method). All chained functions are expected to be\r\n\r\n resolved\r\n so that the final\r\n\r\n done\r\n function was called. The\r\n\r\n catch\r\n function is called instead of\r\n\r\n done\r\n function, when at least one chained function failed\r\n(rejected).
\r\nSee the full description below.
See the samples: [sample]
moveOn.each\r\nThe\r\neach static method of\r\nmove-on module executes all chosen functions at the same time. Each chained function is expected to be either\r\n\r\n resolved\r\n or\r\n\r\n rejected\r\n, so that the final\r\n\r\n done\r\n function was called. The failed\r\n(rejected) function\r\ndoes not stop the further functions execution. It can be used\r\neg. to log the warnings in the\r\n\r\n catch\r\n callback function.
\r\nSee the full description below.
See the samples: [sample]
moveOn.first\r\nThe\r\nfirst static method of\r\nmove-on module executes all chained functions at the same time. It expects the first\r\n(fastest) function to be\r\n\r\n resolved\r\n, so that the\r\n\r\n done\r\n function was called\r\n(similarly to Promises'\r\n \r\n .race\r\n method). When\r\nall functions failed\r\n(rejected), the\r\n\r\n catch\r\n function is called instead.
\r\nSee the full description below.
See the samples: [sample]
list\r\n ,\r\n \r\n config\r\n ,\r\n \r\n done\r\n ,\r\n \r\n catch\r\n )\r\nmove-on module function executes the\r\n \r\n list\r\n functions\r\n sequentially\r\n (one after another) in the chainlist\r\n function\r\n \r\n resolves\r\n , the next\r\n \r\n list\r\n function is called,\r\n and so on...\r\n list\r\n function\r\n \r\n resolves\r\n , the\r\n \r\n done\r\n function is called\r\n once\r\n (it\r\n ends up the module execution)\r\n list\r\n function\r\n \r\n rejects\r\n , the farther\r\n \r\n list\r\n functions and the\r\n \r\n done\r\n function are\r\n not called in the endlist\r\n function\r\n \r\n rejects\r\n , the\r\n \r\n catch\r\n function is called instead\r\n once\r\n (it\r\n ends up the module execution)\r\n list\r\n function can be\r\n \r\n resolved\r\n and | or\r\n \r\n rejected\r\n \r\n multiple times. The forks of chain are created and executed then\r\n [read more]\r\n list\r\n function can execute the inner\r\n move-on module\r\n [read more]\r\n list\r\n ,\r\n \r\n config\r\n ,\r\n \r\n done\r\n ,\r\n \r\n catch\r\n )\r\nmove-on.all static method executes all the\r\n \r\n list\r\n functions\r\n simultaneously\r\n (at the same time)\r\n list\r\n function\r\n \r\n resolves\r\n , the\r\n \r\n done\r\n is\r\n not called immediatelydone\r\n waits, till\r\n all\r\n \r\n list\r\n functions are\r\n \r\n resolved\r\n , to be called\r\n (it\r\n ends up the module execution - after that, all\r\n resolve and\r\n reject calls are ignored)\r\n list\r\n function\r\n \r\n rejects\r\n , the\r\n \r\n done\r\n function is\r\n not called in the endlist\r\n function\r\n \r\n rejects\r\n , the\r\n \r\n catch\r\n function is called instead\r\n once\r\n (it\r\n ends up the module execution - after that, all\r\n resolve and\r\n reject calls are ignored)\r\n list\r\n function\r\n resolves and | or\r\n rejects\r\n multiple times, only the\r\n first call is respected\r\n [read more]\r\n list\r\n function can execute the inner\r\n move-on module\r\n [read more]\r\n list\r\n ,\r\n \r\n config\r\n ,\r\n \r\n done\r\n ,\r\n \r\n catch\r\n )\r\nmove-on.each static method executes all the\r\n \r\n list\r\n functions\r\n simultaneously\r\n (at the same time)\r\n list\r\n function\r\n \r\n resolves\r\n , the\r\n \r\n done\r\n is\r\n not called immediatelydone waits, till\r\n each\r\n \r\n list\r\n function is either\r\n \r\n resolved\r\n or\r\n \r\n rejected\r\n , to be called\r\n (it\r\n ends up the module execution - after that, all\r\n resolve and\r\n reject calls are ignored)\r\n list\r\n function\r\n \r\n rejects\r\n and the\r\n \r\n catch\r\n is called, it\r\n does not end up the module executionlist\r\n function\r\n resolves and | or\r\n rejects\r\n multiple times, only the\r\n first call is respected\r\n [read more]\r\n list\r\n function can execute the inner\r\n move-on module\r\n [read more]\r\n list\r\n ,\r\n \r\n config\r\n ,\r\n \r\n done\r\n ,\r\n \r\n catch\r\n )\r\nmove-on.first static method executes all the\r\n \r\n list\r\n functions\r\n simultaneously\r\n (at the same time)\r\n done\r\n waits, till\r\n the first\r\n (fastest)\r\n \r\n list\r\n function is\r\n \r\n resolved\r\n , to be called\r\n (it\r\n ends up the module execution - after that, all\r\n resolve and\r\n reject calls are ignored)\r\n list\r\n functions\r\n \r\n reject\r\n , the\r\n \r\n done\r\n function is\r\n not called in the endlist\r\n functions\r\n \r\n reject\r\n , the\r\n \r\n catch\r\n function is called instead\r\n once\r\n (it\r\n ends up the module execution - after that, all\r\n resolve and\r\n reject calls are ignored)\r\n list\r\n function\r\n resolves and | or\r\n rejects\r\n multiple times, only the\r\n first call is respected\r\n [read more]\r\n list\r\n function can execute the inner\r\n move-on module\r\n [read more]\r\n list\r\n \r\n config\r\n \r\n done\r\n \r\n catch\r\n \r\n list\r\n [Array: function | array]\r\nlist stores the list of functions, that should be called. It can contain:\r\nconst list = [fnA, fnB, fnC];\r\n const list = [fnA, [obj, fnB, fnC], fnD]\r\n const list = [fnA, [obj, 'fnB', 'fnC'], fnD]\r\n list can contain [Function] items. It may be function, arrow function or object's methodconfig.context\r\n reference\r\n (except arrow functions and already bound functions\r\n [read more])\r\n config.context\r\n referencethis reference for the chosen functions\r\n (except arrow functions and already bound functions\r\n [read more])\r\n list\r\n :\r\n [0] item should indicate the\r\n object or value to be the\r\n this reference for the functions[1],\r\n [2]\r\n , etc... item(s) should indicate the\r\n function(s), that will be bound to the\r\n [0] object or value[0] object or value instead of the\r\n \r\n config.context\r\n \r\n config.bind\r\n setting does not affect the individual\r\n this reference settingconfig.context\r\n \r\n parameter\r\n list\r\n can still contain the\r\n [Function] items next to this [Array] itemlist\r\n loses their\r\nthis reference to the object, they were declared in, what may be undesirable.\r\n\r\n```javascript\r\nconst workers = {\r\n addWorker: function(){},\r\n listEarnings: function(){}\r\n};\r\nconst list = [\r\n workers.addWorker, //this !== workers\r\n workers.listEarnings //this !== workers\r\n];\r\n```\r\n\r\nthis reference to the object, that the methods are declared in, push [Array] item with methods' [String] names into the\r\n list\r\n :\r\n [0] item should indicate the\r\n object, that the methods are declared in[1],\r\n [2]\r\n , etc... item(s) should indicate the [String]\r\n name(s) of the method(s) declared in the\r\n [0] objectthis reference to the\r\n [0] object and are not\r\n bound to the\r\n \r\n config.context\r\n \r\n config.bind\r\n setting does not affect the\r\n this referenceconfig.context\r\n \r\n parameter\r\n list\r\n can still contain the\r\n [Function] items or\r\n [Array] items with functions next to this [Array] item with [String] method's namesconfig\r\n [Object | null]\r\nconfig argument allows to set the following\r\n config properties:\r\n \r\n timeout\r\n ,\r\n \r\n bind\r\n ,\r\n \r\n context\r\n ,\r\n \r\n passContext\r\n \r\n config is set to\r\n null or when it does not define the particular config property or when it defines the config property\r\n incorrectly, the\r\n default value is used for this config property\r\n instead [sample] [sample] [sample]\r\n config.timeout\r\n10000\r\n0, that indicates the\r\n milliseconds\r\n moveOn\r\n :config.timeout starts out counting down\r\n individually for each chained function immediately after it is called.catch\r\n function with the\r\n \r\n timeout error\r\n argument passedmoveOn.all\r\n :config.timeout starts out counting down\r\n once for all chained functions when the module is fired.catch\r\n function with the\r\n \r\n timeout error\r\n argument passedmoveOn.each\r\n :config.timeout starts out counting down\r\n once for all chained functions when the module is fired.catch\r\n function with the\r\n \r\n timeout error\r\n argument passedmoveOn.first\r\n :config.timeout starts out counting down\r\n once for all chained functions when the module is fired.catch\r\n function with the\r\n \r\n timeout error\r\n argument passedresolves\r\n s and\r\n \r\n reject\r\n s that are called\r\n after the\r\n config.timeout pass\r\n are ignored\r\n config.timeout is set to\r\n null or\r\n Infinity, the timeout is\r\n not set at all. If any of the chained function does not\r\n resolve\r\n (or reject), anything happen then and the\r\n \r\n done\r\n or\r\n \r\n catch\r\n function is never called in the endconfig.timeout is not defined, or if it is defined with\r\n incorrect value, the\r\n default value is set insteadmessage:\r\n eg.\r\n \"Timeout. The chained function did not respond in the expected time of 10000 ms.\"\r\n info:\r\n \"timeout\"\r\n code:\r\n \"ETIMEDOUT\"\r\n config.context\r\n{}\r\nconfig.context refers to the object\r\n (or value), that will be used as the\r\n this reference in all\r\n \r\n list\r\n functions,\r\n \r\n done\r\n and\r\n \r\n catch\r\n \r\n config.context's properties can be defined and got in any functionconfig.context can be\r\n any value, as any value can be used as the\r\n this reference in\r\n Function.prototype.bind\r\n [read more]\r\n config.context is used as the\r\n this reference by default, unless you set\r\n \r\n config.bind\r\n to falseconfig.context is also accessible as the parameter, unless you set\r\n \r\n config.passContext\r\n to falseconfig.passContext\r\ntrue\r\nconfig.context object\r\n (or value) is passed through each\r\n \r\n list\r\n function, the\r\n \r\n done\r\n and\r\n \r\n catch\r\n as the\r\n argument:\r\n list\r\n functions: {\r\n 0:\r\n \r\n resolve\r\n ,\r\n 1:\r\n \r\n reject\r\n ,\r\n 2:\r\n \r\n context\r\n }done\r\n function: {\r\n 0:\r\n \r\n reject\r\n ,\r\n 1:\r\n \r\n context\r\n }catch\r\n function: {\r\n 0:\r\n \r\n context\r\n }config.context\r\n as the argument, set\r\n config.passContext to\r\n false\r\n config.context\r\n accessible as the parameter is usefull:\r\n list\r\n functions,\r\n \r\n done\r\n or\r\n \r\n catch\r\n are\r\n arrow functions, that are non-binding and cannot refer to the\r\n \r\n config.context\r\n via\r\n this keywordlist\r\n with\r\n \r\n individually bound\r\n functions or\r\n \r\n methods names\r\n , that do not refer to the\r\n \r\n config.context\r\n via\r\n this keywordlist\r\n functions,\r\n \r\n done\r\n or\r\n \r\n catch\r\n are\r\n already boundconfig.bind\r\ntrue\r\nlist\r\n function,\r\n \r\n done\r\n and\r\n \r\n catch\r\n are bound to the\r\n \r\n config.context\r\n object\r\n (or value), thus the\r\n this keyword refers to the\r\n \r\n config.context\r\n \r\n this reference of all functions, set the\r\n config.bind to\r\n false\r\n this reference for chosen functions, see the\r\n \r\n list\r\n \r\n constructing options\r\n this reference changed anymorereject\r\n ,\r\n \r\n context\r\n )\r\n [Function]\r\ndone is a callback function, that\r\n(in general) is called as the last one, when the\r\n\r\n list\r\n functions have been successfully executed. The\r\ndone is called in a different way and time, depending on which method is called:\r\nmoveOn\r\n The\r\n done is called, when the last function from the\r\n \r\n list\r\n collection is resolved.\r\n done:\r\n [0]\r\n \r\n reject\r\n \r\n [1]\r\n \r\n config.context\r\n \r\n [2],\r\n [3]\r\n , etc... The arguments passed by the last resolved\r\n \r\n list\r\n function moveOn.all\r\n The\r\n done is called, when all\r\n \r\n list\r\n functions are resolved.\r\n done:\r\n [0]\r\n \r\n reject\r\n \r\n [1]\r\n \r\n config.context\r\n \r\n [2]\r\n \r\n resolveMap\r\n \r\n moveOn.each\r\n The\r\n done is called, when all\r\n \r\n list\r\n functions are either resolved or rejected.\r\n done:\r\n [0]\r\n \r\n reject\r\n \r\n [1]\r\n \r\n config.context\r\n \r\n [2]\r\n \r\n resolveMap\r\n \r\n moveOn.first\r\n The\r\n done is called, when the first\r\n (fastest)\r\n \r\n list\r\n function is resolved.\r\n done:\r\n [0]\r\n \r\n reject\r\n \r\n [1]\r\n \r\n config.context\r\n \r\n [2],\r\n [3]\r\n , etc... The arguments passed by the first\r\n (fastest) resolved\r\n \r\n list\r\n function resolveMap objectresolveMap object is passed through\r\n \r\n done\r\n callback when the\r\n \r\n moveOn.all\r\n and\r\n \r\n moveOn.each\r\n method is executed. It stores all arguments that have been passed by each\r\n \r\n list\r\n function's\r\n \r\n resolve\r\n call.resolveMap contains all\r\n \r\n arguments\r\n objects at the\r\n indeces that correspond to the order of\r\n \r\n list\r\n functions calling;\r\n the third\r\n \r\n list\r\n function's arguments are accessible via\r\n resolveMap[2], and so on...\r\n resolveMap properties:\r\n missing It returns the [Array] list of those\r\n \r\n list\r\n functions' indeces\r\n (due to the order of calling) that have not been resolvedresolveMap methods:\r\n forEach\r\n arguments object.\r\n [0] parameter to be the [Function] callback.\r\n arguments object.\r\n {0: arguments, 1: argumentsIndex, 2: resolveMap}\r\n resolveMap.forEach((arguments, argumentsIndex, resolveMap) => {} );\r\n forAll\r\n arguments object.\r\n [0] parameter to be the [Function] callback.\r\n {0: argument, 1: argumentsIndex, 2: itemIndex, 3: resolveMap}\r\n resolveMap.forAll((argument, argumentsIndex, itemIndex, resolveMap) => {} );\r\n context\r\n )\r\n [Function]\r\ncatch is a callback function, that\r\n(in general) is called as the last one, when the\r\n\r\n list\r\n function(s) have failed. The\r\ncatch is called in a different way and time, depending on which method is called:\r\nmoveOn\r\n The\r\n catch is called, when any\r\n \r\n list\r\n function rejects.\r\n catch:\r\n [0]\r\n \r\n config.context\r\n \r\n [1],\r\n [2]\r\n , etc... The arguments passed by the rejected\r\n \r\n list\r\n functionmoveOn.all\r\n The\r\n catch is called, when any\r\n \r\n list\r\n function rejects.\r\n catch:\r\n [0]\r\n \r\n config.context\r\n \r\n [1],\r\n [2]\r\n , etc... The arguments passed by the rejected\r\n \r\n list\r\n functionmoveOn.each\r\n The\r\n catch is called for each\r\n \r\n list\r\n function rejection.\r\n catch:\r\n [0]\r\n \r\n config.context\r\n \r\n [1],\r\n [2]\r\n , etc... The arguments passed by the rejected\r\n \r\n list\r\n functionmoveOn.first\r\n The\r\n catch is called, when all\r\n \r\n list\r\n function rejected.\r\n catch:\r\n [0]\r\n \r\n config.context\r\n \r\n [1]\r\n \r\n rejectMap\r\n \r\n rejectMap objectrejectMap object is passed through\r\n \r\n catch\r\n callback when the\r\n \r\n moveOn.first\r\n method is executed. It stores all arguments that have been passed by all\r\n \r\n list\r\n functions'\r\n \r\n reject\r\n callsrejectMap contains all\r\n \r\n arguments\r\n objects at the\r\n indeces that correspond to the order of\r\n \r\n list\r\n functions calling;\r\n the third\r\n \r\n list\r\n function's arguments are accessible via\r\n rejectMap[2], and so on...\r\n rejectMap methods:\r\n forEach\r\n arguments object.\r\n [0] parameter to be the [Function] callback.\r\n The [Function] callback is called for\r\n each\r\n arguments object.\r\n {0: arguments, 1: argumentsIndex, 2: rejectMap}\r\n rejectMap.forEach((arguments, argumentsIndex, rejectMap) => {} );\r\n forAll\r\n arguments object.\r\n It expects the\r\n [0] parameter to be the [Function] callback.\r\n {0: argument, 1: argumentsIndex, 2: itemIndex, 3: rejectMap}\r\n rejectMap.forAll((argument, argumentsIndex, itemIndex, rejectMap) => {} );\r\n list\r\n function is called with the following arguments passed:\r\n [0]\r\n resolve callback function[1]\r\n reject callback function[2]\r\n \r\n config.context\r\n object\r\n (or value)\r\n [3],\r\n [4]\r\n , etc...\r\n (for\r\n \r\n moveOn\r\n method only) The arguments passed by the\r\n previous\r\n \r\n list\r\n functionresolve and\r\n reject can be called with any number of arguments [sample] [sample] [sample] [sample]\r\n resolve is called with arguments, these arguments will be passed:\r\n moveOn\r\n : for the further\r\n \r\n list\r\n function\r\n (or for the\r\n \r\n done\r\n function, when the last\r\n \r\n list\r\n function resolves)\r\n moveOn.first\r\n : for the\r\n \r\n done\r\n functionmoveOn.all\r\n ,\r\n \r\n moveOn.each\r\n : for the\r\n \r\n done\r\n function in the\r\n \r\n resolveMap\r\n objectreject is called with arguments, these arguments will be passed:\r\n moveOn\r\n ,\r\n \r\n moveOn.all\r\n ,\r\n \r\n moveOn.each\r\n : for the\r\n \r\n catch\r\n functionmoveOn.first\r\n : for the\r\n \r\n catch\r\n function in the\r\n \r\n rejectMap\r\n objectresolve\r\n |\r\n \r\n reject\r\n callsresolve\r\n and\r\n \r\n reject\r\n do not end function execution. In order to end function execution, use\r\n return resolve(); or\r\n return reject();\r\n moveOn.all\r\n ,\r\n \r\n moveOn.each\r\n and\r\n \r\n moveOn.first\r\n methods expect the\r\n \r\n list\r\n functions to call\r\n \r\n resolve\r\n or\r\n \r\n reject\r\n \r\n once\r\n moveOn\r\n \r\n method, as it calls the\r\n \r\n list\r\n functions sequentially, accepts the multiple\r\n \r\n resolve\r\n and\r\n \r\n reject\r\n calls:\r\n list\r\n function calls the\r\n \r\n resolve\r\n twice, it runs the further\r\n \r\n list\r\n functions twice\r\n (the forks are created);\r\n the\r\n \r\n resolve\r\n can be called eg. with different arguments\r\n list\r\n function calls the\r\n \r\n reject\r\n twice, it calls the\r\n \r\n catch\r\n twice;\r\n the\r\n \r\n reject\r\n can be called eg. with different [Error] objects\r\n list\r\n function calls both\r\n \r\n resolve\r\n and\r\n \r\n reject\r\n , it both runs the further\r\n \r\n list\r\n functions and calls the\r\n \r\n catch\r\n \r\n move-on modulelist\r\n function can also contain the\r\n inner\r\n move-on module execution, that has the\r\n \r\n done\r\n argument set to the\r\n \r\n resolve\r\n callback of this\r\n \r\n list\r\n functionmove-on chain of synchronous and asynchronous functionsmove-on module with the user config.context and the arguments passed through the resolve and reject arrow callback functionsmove-on module that rejects\r\n Mind that the second rejected function ends up the execution of further chained functions.\r\n\r\n```javascript\r\nconst moveOn = require('move-on');\r\n\r\nmoveOn([a, b, c], null, onDone, onCatch);\r\n\r\nfunction a(resolve, reject) {\r\n resolve();\r\n}\r\nfunction b(resolve, reject) {\r\n reject('oops!');\r\n}\r\nfunction c(resolve, reject) {\r\n //it's been never called!\r\n resolve();\r\n}\r\n\r\nfunction onDone(reject, context) {\r\n //it's been never called!\r\n}\r\n\r\nfunction onCatch(context, message) {\r\n console.log(message); //oops!\r\n}\r\n```\r\n
\r\n
move-on instructions after resolve call\r\n In order to end up the chained function's execution, call return resolve();\r\n\r\n\r\n```javascript\r\nconst moveOn = require('move-on');\r\n\r\nmoveOn([a, b, c], null, onDone, onCatch);\r\n\r\n/* logs order:\r\n A before\r\n B before\r\n C before\r\n Done!\r\n C after\r\n B after\r\n A after\r\n*/\r\n\r\nfunction a(resolve) {\r\n console.log('A before');\r\n resolve();\r\n console.log('A after');\r\n}\r\nfunction b(resolve) {\r\n console.log('B before');\r\n resolve();\r\n console.log('B after');\r\n}\r\nfunction c(resolve) {\r\n console.log('C before');\r\n resolve();\r\n console.log('C after');\r\n}\r\n\r\nfunction onDone(reject, context) {\r\n console.log('Done!');\r\n}\r\n\r\nfunction onCatch(context, msg) {\r\n console.log(msg); //oops!\r\n}\r\n```\r\nmove-on module and multiple resolve and reject calls\r\n Mind how X, Y and Z functions of the inner module execute between A, B and C chained functions.\r\n\r\n```javascript\r\nconst moveOn = require('move-on');\r\nmoveOn([a, b, c], null, onDone, onCatch);\r\n/* The order of functions execution:\r\n A, X, Y, Z, B, C, Done, Catch, B, C, Done, Catch */\r\n\r\nfunction a(resolve, reject) {\r\n console.log('A');\r\n moveOn([x, y, z], null, () => resolve(), () => reject);\r\n resolve();\r\n}\r\nfunction b(resolve) {\r\n console.log('B');\r\n resolve();\r\n}\r\nfunction c(resolve, reject) {\r\n console.log('C');\r\n resolve();\r\n reject();\r\n}\r\nfunction x(resolve) {\r\n console.log('X');\r\n resolve();\r\n}\r\nfunction y(resolve) {\r\n console.log('Y');\r\n resolve();\r\n}\r\nfunction z(resolve) {\r\n console.log('Z');\r\n resolve();\r\n}\r\nfunction onDone() {\r\n console.log('Done');\r\n}\r\nfunction onCatch() {\r\n console.log('Catch');\r\n}\r\n```\r\n
\r\n Mind how the B and C chained functions are executed twice, by doubleresolvecall in A chained function.\r\n
move-on.all chain\r\n It calls\r\n\r\n```javascript\r\nconst moveOn = require('move-on');\r\n\r\nconst list = [getArticle, getTagList, getCommentSection];\r\n\r\nmoveOn.all(list, { timeout: 5000, passContext: false }, onDone, onCatch);\r\n\r\nfunction getArticle(resolve) {\r\n var xhr = new XMLHttpRequest();\r\n xhr.onreadystatechange = () => {\r\n if (xhr.readyState == 4 && xhr.status == 200) return resolve(xhr.responseText);\r\n };\r\n xhr.open(\"GET\", \"article.js\", true);\r\n xhr.send();\r\n}\r\n\r\nfunction getTagList(resolve) {\r\n var xhr = new XMLHttpRequest();\r\n xhr.onreadystatechange = () => {\r\n if (xhr.readyState == 4 && xhr.status == 200) return resolve(xhr.responseText);\r\n };\r\n xhr.open(\"GET\", \"tags.js\", true);\r\n xhr.send();\r\n}\r\n\r\nfunction getCommentSection(resolve) {\r\n var xhr = new XMLHttpRequest();\r\n xhr.onreadystatechange = () => {\r\n if (xhr.readyState == 4 && xhr.status == 200) return resolve(xhr.responseText);\r\n };\r\n xhr.open(\"GET\", \"comments.js\", true);\r\n xhr.send();\r\n}\r\n\r\nfunction onDone(reject, context, map) {\r\n let article = JSON.parse(map[0][0]);\r\n let tags = JSON.parse(map[1][0]);\r\n let comments = JSON.parse(map[2][0]);\r\n}\r\n\r\nfunction onCatch(err) {\r\n throw new Error(err);\r\n}\r\n```\r\ndonecallback function right after all chained functions are resolved.
\r\n The user's shorterconfig.timeoutis set.
\r\n Therejectcallback functions are not used. In case of error, thecatchcallback function will still be called withconfig.timeouterror.
\r\n All retrieved data is passed through theresolvecallback and accessible in theResolveMapdonecallback function.\r\n
move-on.each inner module\r\n The\r\n\r\n```javascript\r\nconst moveOn = require('move-on');\r\nconst fs = require('fs');\r\nconst path = require('path');\r\n\r\nconst list = [getContentsList, copyFiles];\r\nconst config = {\r\n passContext: false,\r\n context: {\r\n copyFrom: './modules',\r\n copyTo: './prod/modules'\r\n }\r\n};\r\n\r\nmoveOn(list, config, onDone, onCatch);\r\n\r\n\r\nfunction getContentsList(resolve, reject) {\r\n fs.readdir(this.copyFrom, (err, files) => {\r\n if (err) return reject(`Could not get the access to the \"${this.copyFrom}\" path.`);\r\n resolve(files); //the files object will be passed through the second function\r\n });\r\n}\r\n\r\nfunction copyFiles(resolve, reject, files) {\r\n const list = [];\r\n //the moveOn.each will take the same user context to get the access to the paths\r\n const config = { context: this, passContext: false };\r\n //creating the list of chained functions for each files item:\r\n for (let file of files) list.push((resolve, reject) => {\r\n let fromPath = path.resolve(this.copyFrom, file);\r\n let toPath = path.resolve(this.copyTo, file);\r\n fs.copyFile(fromPath, toPath, (err) => {\r\n //the reject call does not abort the module execution in moveOn.each method\r\n if (err) return reject(`The file \"${file}\" could not be copied.`);\r\n resolve(file); //the file path is added to the [Resolved] map, accessible in the final done callback function\r\n });\r\n });\r\n //the inner moveOn.each module - as the done callback - calls the resolve callback of the second copyFiles function with [Resolved] map argument\r\n moveOn.each(list, config, (reject, map) => resolve(map), (err) => console.warn(err));\r\n}\r\n\r\n\r\nfunction onDone(reject, map) {\r\n //the [Resolved] map contains the collection of all passed files paths\r\n //the missing property contains the indeces of all moveOn.each chained functions that have been rejected\r\n let message = !map.missing.length ? 'All files have been successfully moved.' : 'The files have been moved with some errors.';\r\n console.log(message);\r\n}\r\n\r\nfunction onCatch(err) {\r\n throw new Error(err);\r\n}\r\n```\r\nmove-onis used to get the files list asynchronously and then to copy all files asynchronously.
\r\n The innermove-on.eachmodule is injected in the second chained function in order to report the success | failure message for each copied file.
\r\n Each copying failure occurrence callsrejectcallback and logs the warning.
\r\n When all files are (un)successfully copied, thedonecallback function is called, that indicates the end of files copying action.\r\n