Actions
Torque Vault Server » History » Revision 4
« Previous |
Revision 4/11
(diff)
| Next »
Trần Lâm Trường, 08/26/2026 06:48 AM
Torque Vault Server¶
Plans¶
- Migrate the source code from Gitlab to Gitea.
- Switch to
developbranch to continue development. - Standardize responses from API:
- Success response:
- List resource (no pagination):
GET /api/v1/able-work-order?wo_id=1
=>200 OK
- List resource (pagination):
GET /api/v1/work-orders?page=1&page_size=20
=>200 OK
{ "data": [ WorkOrder_Object, WorkOrder_Object, ], "meta": { "page": 1, "page_size": 20, "total_pages": 7 } }- Retrieve detail:
GET /api/v1/work-orders/1
=>200 OK
- Create resource:
POST /api/v1/work-orders
=>201 Created
- Update resource:
PUT/PATCH /api/v1/work-orders/1
=>200 OK
- Delete resource:
DELETE /api/v1/work-orders/1
=>204 No Content
- List resource (no pagination):
- Error response:
- Validation Error:
POST /api/v1/work-orders
=>400 Bad Request
{ "code": "VALIDATION_ERROR", "message": "Validation failed", "errors": { "make": [ "This field is required." ], "employee": [ "This field is required." ] } }- Resource Not Found:
PATCH /api/v1/work-orders/1
=>404 Not Found
- Validation Error:
- Success response:
- Develop an API endpoint for the mobile app home screen to retrieve all work orders whose status is Open, Retorque, Servicing, or Re-servicing.
- Migrate the
Help / Instructionsfeature fromwalmartbranch todevelopbranch. - CI CD integration.
Updated by Trần Lâm Trường about 1 month ago · 11 revisions