Functionality bug: View does not reject incorrect dates

[Jiacheng-y]

To reproduce the bug,

1. input the following command into the command line:
   view t/i mo/0000-12
2. hit enter

Expected: an error message to inform user that the year input is wrong and year 0000 does not exist.

However,

the following display is shown although year 0000 does not exist and is no way a meaningful input for a finance management application in the 21st century.

[nus-se-script]

Team's Response

Intended, this is to avoid overzealous input validation and cater for strange ways that the users may use the product as advised by prof.
for example: users may want to use year 0000 to indicate a special expense or a special income. We do not think it is necessary to limit the year that they can input to improve flexibility of the application so the users can use it however they desire to

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: Thank you for the response.

However, there is no warning for the potentially invalid input of view t/i mo/0000-12 either. Perhaps type.FeatureFlaw would be a more appropriate tag for this bug.

---

❓ Issue severity

Team chose [severity.Low]
Originally [severity.Medium]

• I disagree

Reason for disagreement: [replace this with your explanation]

---