Open dillongoh opened 1 year ago
This stems from the same issue since the validation for the deadlines is handled by the same library, since it would be difficult to validate both fixed date-time formats and natural language formats. A valid input is defined as anything that the library would be able to parse a date-time from. The library is able to parse 2 am out of the 2
in the input string.
[The team marked this bug as a duplicate of the following bug]
Unexpected time to autofill
Entering the command "ap n/test6 d/15-04-2023" gives me the following output:
The program has added a deadline timing of 3am which does not make sense to me as the user. Even if a time was to be displayed, I would expect midnight to be the default time.
[original: nus-cs2103-AY2223S2/pe-interim#1142] [original labels: severity.Low type.FunctionalityBug]
[This is the team's response to the above 'original' bug]
The current expected behaviour is that the app parses all deadline inputs into a date-time output due to the library used to parse natural language/date formats. If no time is provided by the user, the current time is taken as the time to use.
Due to the usage of a library, it would take a lot more effort to remove the time of the output if no time is provided by the user. The user can also edit the deadline to have a 12am time if needed.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
Reason for disagreement: This issue is not a duplicate of the original bug. The original bug is about the unexpected default timing when no time is provided. This bug is about the deadline "+++2" being interpreted as "April 14 2023 2am".
After entering the command "ap n/test123ads d/+++2" it produced this :