nus-se-bot
commented
1 year ago Team's Response
No details provided by team.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Date error message not accurate
For the following date, it tell me that my date format is incorrect although it is not. The more accurate error should be that the date is not a valid one. Therefore verylow since the date error could be more accurate
[original: nus-cs2103-AY2223S1/pe-interim#2961] [original labels: type.FeatureFlaw severity.VeryLow]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
Thank you for the suggestion. We will try to improve our error messages.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.Low]
- [x] I disagree
Reason for disagreement: When typing in invalid date, it gives error message about the format.
When typing in radd s/1 d/28/13/2012 c/CONTENT r/RATING [t/TAGS] and radd s/1 d/30/02/2012 c/CONTENT r/RATING [t/TAGS]... , the error message says Dates can be written as DD/MM/YYYY or DD-MM-YYYY. However the error is not about the input format but about invalid input and input not in scope. It will be better if the error response message is changed or provide more information( like"date out of scope...")