/* A consolidated mechanism for identifying something that generally has a path in the system. Each location references either a depot, a dir, or a file. */ function Location(data) { Object.defineProperties(this, { /* An absolute depot path specification. */ "depotPath": { value: data ? data.depotPath : undefined, enumerable: true, writable: true }, /* */ "depot": { value: data ? data.depot : undefined, enumerable: true, writable: true }, /* */ "dir": { value: data ? data.dir : undefined, enumerable: true, writable: true }, /* */ "file": { value: data ? data.file : undefined, enumerable: true, writable: true }, /* */ "fstat": { value: data ? data.fstat : undefined, enumerable: true, writable: true }, /* If this location indicates a single file, this can be set with the Base64-encoded content of the file. */ "content": { value: data ? data.content : undefined, enumerable: true, writable: true } }); } module.exports = Location;
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 19553 | swellard | Move and rename clients | ||
//guest/perforce_software/helix-web-services/main/source/clients/2016.1.0/javascript/lib/models/location.js | |||||
#2 | 19169 | tjuricek | JavaScript Client SDK jobs CRUD test, with supprt for "additionalProperties" in the swagger definition. | ||
#1 | 19053 | tjuricek |
Rebuild JavaScript Client SDK. The JavaScript client now is a "typed" approach that tends to be similar in approach to the other clients, based on the swagger definition for the platform version. Importantly, client SDK tests are individual scripts (that run under node) that are actually controlled via TestNG. This approach now lets us use a consistent test reporting format so we can at least collect reports from each of the jobs. The documentation is still in progress, that I want to validate as the tests are generated. |