Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
ACQ Sprint 60
-
3
-
EBSCO - FSE
Description
Overview:
Once the APIs have been defined and RMB is generating stub code, the APIs need to be implemented. This story specifically pertains to the implementation of the invoices API.
- POST /invoice-storage/invoices
- GET /invoice-storage/invoices
- GET /invoice-storage/invoices/<id>
- PUT /invoice-storage/invoices/<id>
- DELETE /invoices-storage/invoices/<id>
See the API Listing for details: https://docs.google.com/spreadsheets/d/1se-a2owRfHLG5eaAZglx4vLvRClCKGp2wZCfD39ZJRY/edit#gid=894044560
Approach:
- Use of PgUtil is encouraged to help with simplicity and maintainability
- Base classes should be used when appropriate to reduce the amount of boilerplate/duplicate code (applies to tests as well)
Acceptance Criteria:
- The 5 APIs are implemented
- Unit test coverage is at 80% or higher
TestRail: Results
Attachments
Issue Links
- blocks
-
MODINVOICE-20 Implement POST /invoicing/invoices
-
- Closed
-
- is blocked by
-
MODINVOSTO-2 Define APIs
-
- Closed
-
- relates to
-
MODINVOICE-22 Implement GET /invoice/invoices
-
- Closed
-
-
MODINVOSTO-4 Implement Basic CRUD APIs for invoice-lines
-
- Closed
-
-
UXPROD-720 Allow user to create Invoice
-
- Closed
-