var Stream = require('stream'); function prop(propName) { return function (data) { return data[propName]; }; } module.exports = unique; function unique(propName) { var keyfn = JSON.stringify; if (typeof propName === 'string') { keyfn = prop(propName); } else if (typeof propName === 'function') { keyfn = propName; } var seen = {}; var s = new Stream(); s.readable = true; s.writable = true; var pipes = 0; s.write = function (data) { var key = keyfn(data); if (seen[key] === undefined) { seen[key] = true; s.emit('data', data); } }; var ended = 0; s.end = function (data) { if (arguments.length) s.write(data); ended++; if (ended === pipes || pipes === 0) { s.writable = false; s.emit('end'); } }; s.destroy = function (data) { s.writable = false; }; s.on('pipe', function () { pipes++; }); s.on('unpipe', function () { pipes--; }); return s; }
# | 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/unique-stream/index.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. |