Support modifying a transaction category #32
2 Participants
Notifications
Due Date
No due date set.
Depends on
#28 Implements GET /categories
personal-finance/datastore
Reference: personal-finance/datastore#32
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "feature/26-add-category"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
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.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 #2313d752e69ato9e58641001467afae68ftoca692e9aafca692e9aafto50e8269120