Return category on /transactions #33

Closed

satprog wants to merge 2 commits from feature/26-get-transaction-category into main

satprog commented

2024-06-24 20:46:05 +00:00

Owner

Issue #26

satprog added 6 commits

2024-06-24 20:46:05 +00:00

Implements /transactions POST method 4c82ca0e2b

It adds the method to the OpenAPI spec and generates a new server
config. The requirement for the ID on the Transaction component is
removed, so that it can be reused for insertions.
It also adds two new middlewares, a logging and a spec validator. If a
request does not follow the spec, a 400 is returned immediately.

Issue: #18

Implements /transactions PUT method 55bd87c864

Adds PUT method to OpenAPI spec.

Given that the transaction IDs are generated on server-side, for the PUT
method to remain idempotent, it can only update existing transactions.

It also adds a TransactionExists method on the DAL.

Issue: #20

Fix resources naming scheme 18c93b6c0f

The accepted practice is to retain the collection name even for a single
resource operation, like getting a specific transaction.

Also moves the PUT /transactions to /transactions/{id} which makes it
clearer that it can only be applied to an already created transaction.

Implements GET /categories 9ac249199b

Adds type to OpenAPI. Feature done and tested E2E.
Adds common utilities package named "golang" to overcome language
deficiencies.

Issue #27

Support modifying a transaction category 13d752e69a

through the PUT /transactions/{transactionId} method.

Restrict the PUT to changing only the category. The other existing
attributes should remain immutable.
Remove the body of the PUT response, it isn't required, and it was
returning a 204, which shouldn't have it.

This patch also extracts the CategoryName as a separate component on the
OpenAPI spec, so that it can be reused on the Transaction.

Issues #26 and #23

Return category on /transactions 92aa51c664