Let's tweak the docs/README.md (which is used as the user guide)
to fit Duke better. Specifically,

1. mention product name in the title
2. mention adding a product screenshot and a product intro
3. tweak the flow to describe feature-by-feature

BMO now echoes back everything you say to him

abstracted tasks into a separate class

Error handling now handles these:
1. general error
2. index provided is out of range
3. task to be done is already done
4. task to be redone is already not done
5. no index was provided
6. user input add with nothing following up
7. incorrect deadline input format
8. incorrect todo input format
9. incorrect event input format

The formatter now recognises date time strings with "/" to express dates as valid. Previously, strings containing "/" would throw a format error and not accept it as a valid string

When user adds a task with a date time variable, the string will be formatted into a LocalDateTime object that is stored in the task object.

A more oop

This reverts commit 16a7afd, reversing
changes made to b3a931f.

This reverts commit 5f73efc, reversing
changes made to e5370f5.

Add assertions to the BMO, Storage and TaskList classes

Several methods in these classes require important assumptions to hold true in order for the program to run.

Assertions for these conditions to the code helps the debugging process.

Let's add assertions to these classes.

Parse parse method is too long and handles both input type checking and input format checking.

Having smaller methods to handle the different types of possible inputs makes the code more readable.

Let's update the parser method to handle only input type checking, and abstract out input format checking to appropriate methods.

Add assertions to Deadlines and Events classes

Parse parse method is too long and handles both input type checking and input format checking.

Having smaller methods to handle the different types of possible inputs makes the code more readable.

Let's update the parser method to handle only input type checking, and abstract out input format checking to appropriate methods.

TaskList constructor method is too long and has duplicated code.

Swapping around the try block to encapsulate the switch block instead of vice versa helps remove duplicate code and improve readability.

Let's update the TaskList constructor method and reduce duplicate codes

A-assertions

A-code quality