Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
-
ACQ Sprint 56, ACQ Sprint 57
-
3
-
Thunderjet
Description
In at least one case (non-unique po-number), we return a text/plain response. In the interest of consistency, we should return application/json conforming to the error schema from the raml project, just as RMB does for 422s.
We should also make sure we're specifying a useful value in the 'code' field, e.g. poNumberNotUnique. These codes will likely be mapped to error messages presented to the user in the UI.
Acceptance Criteria:
- All (or as many as possible) error conditions return an application/json response conforming to the error schema from the raml project
- useful values are provided in the 'code' field
TestRail: Results
Attachments
Issue Links
- relates to
-
UIOR-71 Adjustments to po_number field on create/edit order forms
-
- Closed
-
-
UIOR-73 Validate user-specified po_number values (order creation form)
-
- Closed
-
-
UIOR-74 Validate user-specified po_number values (order edit form)
-
- Closed
-
-
UXPROD-1388 Create New Purchase Order Lines
-
- Closed
-
-
MODORDERS-89 Create POST /orders/po-number/validate endpoint for validating a po_number
-
- Closed
-