Open BenardoTang opened 3 years ago
This is an expected and designed behaviour. For non-parsable dates, the command accepts it as String. Because there can be legitimate use cases like this:
deadline ddl -by this Friday evening
Team chose [response.Rejected
]
Reason for disagreement: [replace this with your reason]
Team chose [type.FunctionalityBug
]
Originally [type.FeatureFlaw
]
Reason for disagreement: [replace this with your reason]
When i try to input an invalid date and time for the event command, there is no error thrown and the program adds the task into the list.