Open Holy-An opened 2 weeks ago
Thank you for the report. As you can see the defined format was yyyy-MM-dd, so it will take the year with more than 4 letters as invalid format.
Team chose [response.NotInScope
]
Reason for disagreement: The team’s response addresses the date format but does not explain the inconsistency in error messages, as the year 10000 is also from the future. Consistent error messages are critical for user clarity. Both errors could follow the same format, e.g., "Error creating transaction: Invalid date/time. Please ensure it is in yyyy-MM-dd HHmm format and not a future date." , or simply "Error creating transaction: you are adding a transaction from the future!", as rejecting the 5 digits for years is not really necessary
The error for the first message could've been the same as the second.