Open vishandi opened 2 years ago
As mentioned in the UG, the date that users key in must not be in the past. Clearly, this is just an example of how you should key in the command. In fact, any date that we put will eventually be a date of the past.
Team chose [response.Rejected
]
Reason for disagreement: Well, that is why I put it as a FunctionalityBug, because the example you provided is unusable and it is different than what the rule said in the UG. I really hate to say this, but your argument "In fact, any date that we put will eventually be a date of the past." is wrong. You can make the error message's date dynamic and to be some date in the future of the user's system's date by using LocalDate, making the example works.
Team chose [severity.VeryLow
]
Originally [severity.Low
]
Reason for disagreement: As stated in the guideline, severity.VeryLow should only be cosmetic issues, in which this is not the case.
The example is unusable.