nus-se-script
commented
2 years ago Team's Response
No details provided by team.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Inaccurate error message when inputting invalid dates
Issue
(see image below)
[original: nus-cs2103-AY2122S2/pe-interim#2505] [original labels: severity.VeryLow type.DocumentationBug]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
An invalid date format was inputted. "30" is an invalid date for "February" and hence is an invalid format using the "dd-MM-uuuu HH:mm" format which uses the year of era formatting and considers the given input as an invalid format.
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 response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
:question: Issue type
Team chose [type.FunctionalityBug]
Originally [type.DocumentationBug]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
Steps to reproduce:
1) Enter an invalid date:
edit 1 idt/33-04-2022 15:00Expected behaviour:
Valid error message.
Actual behaviour:
Valid error message, however the prompt suggests for the user to key in a date with format "dd-MM-uuuu", where "uuuu" is given as a format when it is likely "yyyy" or "YYYY".
Screenshot: