| Name | Modified | Size |
|---|---|---|
| .. | ||
| models | ||
| alpha_api.js | 9 years ago | |
| api_client.js | 9 years ago | |
| default_api.js | 9 years ago | |
| models.js | 9 years ago |
| Change | User | Description | Committed |
|---|---|---|---|
| 19553 | swellard | Move and rename clients | 9 years ago |
| 19202 | tjuricek | Revised documentation for the Ruby Client SDK; removed obsolete methods and definitions, a...nd restyled a lot of the tables. « | 9 years ago |
| 19169 | tjuricek | JavaScript Client SDK jobs CRUD test, with supprt for "additionalProperties" in the swagge...r definition. « | 9 years ago |
| 19125 | tjuricek | JavaScript Client SDK commands tests with fix for passing around array query parameter arg...uments. « | 9 years ago |
| 19122 | tjuricek | JavaScript Client SDK change-related tests. | 9 years ago |
| 19098 | tjuricek | JavaScript Client SDK labels spec CRUD tests. Identified another parameter naming confl...ict, which only pops up in the javaScript client because I didn't choose to automatically rename parameters for people. (I don't think it's a good idea to just say "label0", "label1", etc., especially when they're different types.) « |
9 years ago |
| 19095 | tjuricek |
JS Client SDK branch spec CRUD test Added URL component encoding on path parameters. |
9 years ago |
| 19067 | tjuricek | Add handling to deal with IllegalArgumentException as general "400" level errors from user...s. The different client APIs just need to have their respective techniques provide the error status. « |
9 years ago |
| 19065 | tjuricek | Revised Javascript Client SDK documentation to meet the new API, with fixes. Added a co...uple of basic tests, and added archival of the different testng XML output. The main major fix is to handle array output better. « |
9 years ago |
| 19053 | tjuricek | Rebuild JavaScript Client SDK. The JavaScript client now is a "typed" approach that ten...ds 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. « |
9 years ago |