Invalid Date Time value successfully parsed

Bug Description

310420251400 which translates to 31-04-2025 14:00 is not a valid date time and not leap year or leap day related, however providing it as a date time input results in 30-04-2025 14:00 being the parsed value.

Steps to Reproduce

add cn/Google n/John Doe p/98765432 e/johnd@example.com a/311, Clementi Ave 2, #02-25 tt/310420251400 i/Birthday: 12 May 2001 s/5000 pl/Java t/friends t/owesMoney pri/2

Expected Behavior

The command should fail due to invalid date time provided.

Screenshots

_{[original: nus-cs2103-AY2324S2/pe-interim#271] [original labels: type.FunctionalityBug severity.Low]}

Team's Response

Thank you for raising this issue. While we acknowledge that this may cause inconvenience to some users, addressing this particular issue is currently not within our scope due to existing project priorities and resource constraints and we have mentioned how we handle leap dates in the UG. Our team is currently focused on addressing critical bugs and implementing essential features to enhance user experience. However, we have noted your feedback and will consider it for future updates to handle leap dates better. Thank you for your understanding.

nus-cs2103-AY2324S2 / pe-dev-response