-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Timestamps for Task #12
Comments
I think that And I think these values ( |
Currently there is a field called done, which is a Boolean. It defines if the task is done or not. I see your point right there. Do you want to take this issue? |
Yeah, I think I could take it. I'm in :) |
OK I assigned you to this issue. Please bear in mind that register page is not working right now, so you have to register through Postman or cURL #4 Also, don't forget to check the Todo API and make sure you update the API with timestamps. Good luck! |
Now that we have a fully functional task system that connects to the REST API, there is some minor changes to the data stored in MongoDB.
So I need fields in the Model that stores timestamps for saved task, such as created_at and modified_at.
But I am hesitating to decide whether to add one field called done_at or not. I mean sure, modified_at will store timestamps when there is modifications to the task such as edit and marked as done. But, what is the best practice? Should you separate done_at with modified_at or combine them in modified_at?
The possibility is that when you have done_at fields, you can gather data of "Task cleared before 31st October". If you only have modified_at, you can only gather data of "Task modified before 31st October".
In conclusion: Add created_at and modified_at field in Todo Model, and decide whether to add one field called done_at or not.
What are your thoughts? Comment down below and maybe try some PR.
Thank you very much
The text was updated successfully, but these errors were encountered: