Open nus-se-script opened 1 day ago
We think that this is not really an issue, as it is logical that day can take any value between 1 and 31. This was also explained specifically in the user guide (It was mentioned that days can be between 1 and 31 and months can be between 1 and 12) The reason why it was written as ‘d’ and not ‘dd’ and similarly with month was to indicate that leading zeros are not necessary in the input. ‘dd’ would imply that one would have to write 01/11/2024 instead of 1/11/2024. This notation is commonly accepted as seen below.
Source: https://docs.oracle.com/cd/E41183_01/DR/Date_Format_Types.html
This idea about leading zeros was also clearly specified in the user guide, so we believe that this is not an issue.
Furthermore, this was mentioned in the DG, under Planned Enhancement Point 8,
We plan to make this clearer with future iterations.
--
The UG specifies the date format to be d/M/yyyy, this format is confusing to users since date and month inputs can have double digits.
[original: nus-cs2103-AY2425S1/pe-interim#2676] [original labels: severity.Low type.DocumentationBug]