To conform better to REST principles, I would suggest replacing/removing the imperative file actions from the following endpoints:
POST /tasks/{taskId}/uploaddeliverable => POST /tasks/{taskId}/deliverableGET /tasks/{taskId}/downloaddeliverable => GET /tasks/{taskId}/deliverable
similarly:
POST /jobs/{jobId}/assets/uploadfile => POST /jobs/{jobId}/assets , I think we don't need the uploadfile suffix, since we are actually creating an asset, where the file itself is just a parameter
GET /jobs/{jobId}/assets/{assetId}/downloadfile => GET /jobs/{jobId}/assets/{assetId}/file => since we are accessing the "file" related to the asset specified by its id
Alino
commented
5 years ago
To conform better to REST principles, I would suggest replacing/removing the imperative file actions from the following endpoints:
POST /tasks/{taskId}/uploaddeliverable=>POST /tasks/{taskId}/deliverableGET /tasks/{taskId}/downloaddeliverable=>GET /tasks/{taskId}/deliverablesimilarly:
POST /jobs/{jobId}/assets/uploadfile=>POST /jobs/{jobId}/assets, I think we don't need theuploadfilesuffix, since we are actually creating an asset, where the file itself is just a parameterGET /jobs/{jobId}/assets/{assetId}/downloadfile=>GET /jobs/{jobId}/assets/{assetId}/file=> since we are accessing the "file" related to the asset specified by its id