feat: add start field to task panel#283
Conversation
|
Thank you for opening this PR! Before a maintainer takes a look, it would be really helpful if you could walk through your changes using GitHub's review tools. Please take a moment to:
More information on how to conduct a self review: This helps make the review process smoother and gives us a clearer understanding of your thought process. Once you've added your self-review, we'll continue from our side. Thank you! |
There was a problem hiding this comment.
added DatePicker component for start date field in task creation
There was a problem hiding this comment.
Added start parameter to addTaskToBackend function and conditional logic to include in request body
There was a problem hiding this comment.
Replaced empty string with actual start date "2025-03-01"
Hell1213
left a comment
There was a problem hiding this comment.
Completed self-review . Backend and frontend properly handle optional start field. Tests passing. Ready for review.
c744b49 to
1285315
Compare
|
Hey @its-me-abhishek, |
|
Please checkout for conflicts introduced by the recent merge |
thanks, will resolve all conflicts and push shortly |
1285315 to
f233998
Compare
Added start date field support to task creation, allowing users to set when a task begins.
Backend: Added start field to AddTaskRequestBody model and AddTaskToTaskwarrior function
Frontend: Added start date input field in task creation dialog
Contributes to Add more Fields to the Add Task Panel #188
Checklist
npx prettier --write .(for formatting)gofmt -w .(for Go backend)npm test(for JS/TS testing)Additional Notes
The start field follows the same pattern as other optional date fields (due, wait, entry). Empty strings are used to indicate when no start date is set, consistent with existing codebase conventions.
Demo:
Screencast.from.2025-12-19.17-05-17.mp4