PUT For Habit Log #3

Open
opened 2026-10-07 20:40:00 -05:00 by fenskesd · 0 comments
Owner

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.

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.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
fenskesd/Steadfast-API#3
No description provided.