/*jshint node:true */ "use strict"; var eos = require('end-of-stream'); var consume = require('stream-consume'); module.exports = function (task, done) { var that = this, finish, cb, isDone = false, start, r; finish = function (err, runMethod) { var hrDuration = process.hrtime(start); if (isDone && !err) { err = new Error('task completion callback called too many times'); } isDone = true; var duration = hrDuration[0] + (hrDuration[1] / 1e9); // seconds done.call(that, err, { duration: duration, // seconds hrDuration: hrDuration, // [seconds,nanoseconds] runMethod: runMethod }); }; cb = function (err) { finish(err, 'callback'); }; try { start = process.hrtime(); r = task(cb); } catch (err) { return finish(err, 'catch'); } if (r && typeof r.then === 'function') { // wait for promise to resolve // FRAGILE: ASSUME: Promises/A+, see http://promises-aplus.github.io/promises-spec/ r.then(function () { finish(null, 'promise'); }, function(err) { finish(err, 'promise'); }); } else if (r && typeof r.pipe === 'function') { // wait for stream to end eos(r, { error: true, readable: r.readable, writable: r.writable && !r.readable }, function(err){ finish(err, 'stream'); }); // Ensure that the stream completes consume(r); } else if (task.length === 0) { // synchronous, function took in args.length parameters, and the callback was extra finish(null, 'sync'); //} else { // FRAGILE: ASSUME: callback } };
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 19553 | swellard | Move and rename clients | ||
//guest/perforce_software/helix-web-services/main/source/clients/2016.1.0/javascript/node_modules/orchestrator/lib/runTask.js | |||||
#1 | 18810 | tjuricek |
First-pass at JavaScript client SDK. JavaScript requires Node with Gulp to "browserfy" the library. It's the easiest way I found to use the swagger-js project; bundle up a wrapping method. There is no JavaScript reference guide. The swagger-js doesn't really document what they do very well, actually. Overall I'm not particularly impressed by swagger-js, it was hard to even figure out what the right method syntax was. We may want to invest time in doing it better. This required setting CORS response headers, which are currently defaulted to a fairly insecure setting. |