// SIGKILL can't be caught, and in fact, even trying to add the // listener will throw an error. // We handle that nicely. // // This is just here to get another few more lines of test // coverage. That's also why it lies about being on a linux // platform so that we pull in those other event types. Object.defineProperty(process, 'platform', { value: 'linux', writable: false, enumerable: true, configurable: true }) var signals = require('../../signals.js') signals.push('SIGKILL') var onSignalExit = require('../../') onSignalExit.load()
# | 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/signal-exit/test/fixtures/sigkill.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. |