SQL-Ledger GL routes according to OpenAPI specifications

by Hashim, Friday, September 22, 2023, 04:44 (219 days ago) @ Hashim

Update regarding development, where we are till now.

1. Route to update a transaction has been created. This is essentially the same as as the create route but if there is an "id" supplied in the route like post '/gl/transactions/{id}', it will be treated as an update request. The complete object GL object payload will be required. We are using post instead of put, since on the back end, the code for the route is also essentially the same/it wouldn't make much sense to create a separate route for this specially since the processing is almost identical to the create route. We can change this later if there's anything special required for the update route.

2. Route to delete a transaction has been added.

3. Filters for the get transactions route have been added. The filters available right now are startDate
endDate
description
notes
reference
accno
but this can be updated/have more added as needed.

4. Route definitions now follow:
api/client/{client} structure.

5. Testing URL has been updated to:
https://api.mnapk.com/api/client/ledger28

All of these changes are reflected in:
https://app.swaggerhub.com/apis/HASHIM1SAQIB/SqlLedgerRest/1

Link to repo:
https://github.com/HashimSaqib/Sql-Ledger-REST


Complete thread:

 RSS Feed of thread