Skip to content
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

Branch c update #5

Merged
merged 3 commits into from
Sep 13, 2024
Merged

Branch c update #5

merged 3 commits into from
Sep 13, 2024

Conversation

MAOXIONGKAI
Copy link
Owner

No description provided.

User can now use update [task number] taskName [tokens] field value to
specify the fields within the task that they want to update.

For example: update 4 Hello /by 2024-05-11 changes the 4-th task's name
in the task list to Hello. If the task is Deadline, then change its
due date to May 11 2024, else a warning message will be prompted by
gopher
Currently user can include tokens that are not recognized by the task
type as part of the task name, which is not a very good way of handling
updating logic because including token as part of the name leads to
more confusion and can make the app hard to use if user is careless

Hence, checks are added to the update logic of each type of task to
raise error message to the user when they accidentally type in invalid
tokens when updating a task. By reinforcing this we can make the whole
task management app cleaner and less error-prone
The current parsing logic is in individual task type's update method,
which makes the code very messy and hard to organize.

Hence, the parsing logic are shifted to Parser.java to make the code
more readable and adhere to code quality and standards
@MAOXIONGKAI MAOXIONGKAI merged commit 6c913e8 into master Sep 13, 2024
6 checks passed
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.

1 participant