Open jvoss opened 6 years ago
In gitlab by @jvoss on Oct 23, 2017, 03:48
changed the description
In gitlab by @mkosmo on Nov 10, 2017, 04:59
Of note, VATUSA results aren't pretty formatted.
404 on VATUSA returns:
{ "status": "error", "msg": "", "exception": "Symfony\Component\HttpKernel\Exception\NotFoundHttpException" }
In gitlab by @mkosmo on Nov 10, 2017, 05:00
Example of not-pretty format.
In gitlab by @jvoss on Nov 10, 2017, 20:56
404 on VATUSA returns:
{ "status": "error", "msg": "", "exception": "Symfony\Component\HttpKernel\Exception\NotFoundHttpException" }
Did the status code for this response actually return code 404 or was it 200?
In gitlab by @jvoss on Nov 10, 2017, 23:24
mentioned in commit 7bc817eb1e84c0867634c9432848ace2624d1681
In gitlab by @jvoss on Nov 10, 2017, 23:25
Please checkout branch 'jvoss-api' 7bc817eb and validate VATUSA API calls. I believe I have all of the ones you provided output for tested.
Will also need to double check me and make sure that all of the data types match. I often had CID as a string when VATUSA returns an integer, etc.
In gitlab by @jvoss on Nov 11, 2017, 15:17
mentioned in issue #22
In gitlab by @jvoss on Nov 12, 2017, 20:23
GET /transfer response:
{"status":"success","transfers":[{"id":701517,"cid":1398598,"fname":"Gilberto","lname":"Gonzalez","rating":1,"rating_short":"OBS","email":"
In gitlab by @jvoss on Oct 23, 2017, 03:46
Need to validate the action and response of each of the VATUSA API functions and how the fake API middleware acts in comparison.
Please use the following URL for testing with ARTCC manager: https://artccmgr-dev.herokuapp.com/fakeapi/VATUSA
The fake API will take any API key.
This URL should should be used in the exact same manner as https://api.vatusa.net
Example: https://artccmgr-dev.herokuapp.com/fakeapi/VATUSA/[key]/cbt/block --relates to-- https://api.vatusa.net/[key]/cbt/block