Open Jun-How opened 1 year ago
Thank you for raising this issue. Negative years, as documented, is correct as per the state of our app during the PE, so it is technically not a documentation bug. However, we agree that it is a feature flaw, and have addressed this in our DG’s appendix in point no. 6 (which references point no. 5). In short, we plan to set a boundary on the valid years to be [1800, now + 10).
Team chose [response.Rejected
]
Reason for disagreement: Thank you for your response. From a logical perspective, negative years are invalid. Thus, the user may be confused as to why negative years are considered valid. Furthermore, there is no example shown in the user guide that negative years are used, thus the user may be unsure how it actually looks like when input in a command. I understand that you have acknowledged this issue in the developer guide, but the one I raised comes from the user guide, where the user would be easily confused about when they would use negative years. Hence, I would consider this a documentation bug since it concerns the user who is reading it.
In the UG, it is stated that "The range of valid years is from -9999 to 9999." but negative years should be invalid.