PUT For Habit Log #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Currently, when we cycle through our Habit Log statuses; we create new logs each time. We really should be using POST when creating a new one, and PUT when updating one.
We should reject a put for a task if it is already resolved during that time period. Example: A Weekly task being PUT on Friday should get an error response if we already did one Tuesday.
Getting an error code should tell us to use the PUT instead to update the existing log instead.