Skip to content

Add end field to Add Task feature#196

Closed
Eshaan-byte wants to merge 2 commits into
CCExtractor:mainfrom
Eshaan-byte:add-start-field-to-task
Closed

Add end field to Add Task feature#196
Eshaan-byte wants to merge 2 commits into
CCExtractor:mainfrom
Eshaan-byte:add-start-field-to-task

Conversation

@Eshaan-byte
Copy link
Copy Markdown
Contributor

Description

This PR adds support for the end field when creating tasks through the UI, allowing users to specify an end date for their tasks directly from the Add Task dialog.

This is part of the ongoing effort to make more task fields editable through the frontend interface, as outlined in the original issue.

  • Fixes: #(issue_number_for_end_field)
  • Related to: #(the_main_issue_number_about_making_fields_editable)

Changes Made

Frontend Changes:

  • Added end field to newTask state in Tasks component
  • Added End DatePicker input to both Add Task dialogs (main view and empty state view)
  • Updated handleAddTask function to accept and pass end parameter
  • Updated addTaskToBackend API function to send end field to backend
  • Reset end field properly when form is cleared

Backend Changes:

  • Added End field to AddTaskRequestBody model
  • Updated AddTaskHandler controller to extract and process end field
  • Updated AddTaskToTaskwarrior function signature to accept end parameter
  • Added end: attribute to taskwarrior command when end value is provided

- Add start date field to frontend Add Task dialog (desktop & mobile)
- Update newTask state to include start field
- Update addTaskToBackend API call with start parameter
- Add Start field to backend AddTaskRequestBody model
- Update AddTaskHandler to extract and pass start field
- Update AddTaskToTaskwarrior to include scheduled date in taskwarrior command
- Use 'scheduled' attribute in taskwarrior (maps to start date)
- Start field is optional and only added if provided

Implements CCExtractor#188 (Start field)
This commit adds support for the 'end' field when creating tasks through the UI.

Frontend changes:
- Added 'end' field to newTask state
- Added End DatePicker input to both Add Task dialogs
- Updated handleAddTask function to accept and pass 'end' parameter
- Updated addTaskToBackend to send 'end' to the backend API

Backend changes:
- Added 'End' field to AddTaskRequestBody model
- Updated AddTaskHandler to extract and process 'end' field
- Updated AddTaskToTaskwarrior function to accept and handle 'end' parameter
- Added 'end:' attribute to taskwarrior command when provided
@its-me-abhishek
Copy link
Copy Markdown
Collaborator

This seems to implement Start as Scheduled, while mentioning addition of End field in the Add Task panel, hence is confusing and not relevant. Closing For Now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants