Description: When users input an invalid date (e.g. 31 Feb 1999), the app automatically modifies it to a valid date (e.g. 28 Feb 1999) without notifying the user of the issue. Although it is mentioned in the UG that such invalid input may lead unexpected behaviour, it is not specified clearly to the user what will happen. According to the rubrics, the lack of proper handling (either blocking or warning) potentially harmful invalid inputs can be considered a type.FeatureFlaw bug.
steps to reproduce:
1.list all persons and call meetings, click on Bernice Yu(index 2) and enter command 'schedule 2 st/31-02-1999 09:00 et/31-02-1999 10:00 l/The Terrace' to add a meeting:
after add meeting command:
As shown, the invalid input date is automatically adjusted to be 28 February without any blocking or warning. One way to improve is to show a prompt message for invalid inputs like this to warn the user instead of modifying it automatically.
Description: When users input an invalid date (e.g. 31 Feb 1999), the app automatically modifies it to a valid date (e.g. 28 Feb 1999) without notifying the user of the issue. Although it is mentioned in the UG that such invalid input may lead unexpected behaviour, it is not specified clearly to the user what will happen. According to the rubrics, the lack of proper handling (either blocking or warning) potentially harmful invalid inputs can be considered a type.FeatureFlaw bug.
steps to reproduce:
1.list all persons and call meetings, click on Bernice Yu(index 2) and enter command 'schedule 2 st/31-02-1999 09:00 et/31-02-1999 10:00 l/The Terrace' to add a meeting:
after add meeting command:
As shown, the invalid input date is automatically adjusted to be 28 February without any blocking or warning. One way to improve is to show a prompt message for invalid inputs like this to warn the user instead of modifying it automatically.