Open JerryO3 opened 6 months ago
Thanks for pointing this out! Users are informed of the correct date time format in the user guide. So they are not expected to guess the format. Additionally sample data is provided at start-up with the correct data format on display. However, it would be better if the error message informed them of the correct format.
Team chose [response.NotInScope
]
Reason for disagreement: I refer to the CS2103T Website for below:
The lack of error specificity in the "invalid date" error message is highly ambiguous, especially since date in this case refers to both date and time (optional). It would have been better to include a more specific error message, or plan to include it in planned enhancements in future. Referring to the above image, even if the UG does mention the syntax, a more specific error message would go a long way to alleviate confusion.
Since it is a change requiring minimal effort whose current implementation causes confusion for users who use the article adding feature (which is most users!), I do not believe it should be categorized as response.NotInScope
as per the guidelines below:
There is no mention of the format to input time into the command box. The error message only shows invalid date, so there users have to guess what is the correct time input format.
Input: add -a h/NotLeapYear d/02-02-2023 1403 s/draft