The planned enhancements only mentioned "Enhancing commands involving date time inputs to check for invalid date inputs for specific months" but did not mention to check for very wrong years which is likely a typo of the user.
Steps to reproduce: advance a user with interview date at a very far date in the future such as year 2600
Expected: Warning that the date of interview is likely a typo
Actual: Allows the date to be set
For more detail, please refer to the screenshot below:
The planned enhancements only mentioned "Enhancing commands involving date time inputs to check for invalid date inputs for specific months" but did not mention to check for very wrong years which is likely a typo of the user.
Steps to reproduce: advance a user with interview date at a very far date in the future such as year 2600
Expected: Warning that the date of interview is likely a typo
Actual: Allows the date to be set
For more detail, please refer to the screenshot below:
[original: nus-cs2103-AY2223S2/pe-interim#1678] [original labels: type.FunctionalityBug severity.Medium]