Describe the bug
Invalid dates are being allowed by the client app and stored in the database, leading to errors in the ETL service.
example: "Dec 21, -10323."
This issue occurs when changing the duration rather than selecting or entering a date directly.
Expected behavior
The application should validate the date input to ensure it is a valid and realistic date before allowing it to be stored in the database. An error message should be displayed for invalid dates.
Screenshots
Additional context
Invalid dates in the database are causing downstream errors in the ETL service. Error logs from the ETL service are attached for reference.
wrror_logs_invalid_date_range.txt
Developer Checklist
Developer fixing the bug should fill this checklist.
[ ] Does the fix require extensive regression testing?
[ ] Are you mentioning the required scenarios that could be affected?
Describe the bug Invalid dates are being allowed by the client app and stored in the database, leading to errors in the ETL service. example: "Dec 21, -10323." This issue occurs when changing the duration rather than selecting or entering a date directly.
Expected behavior The application should validate the date input to ensure it is a valid and realistic date before allowing it to be stored in the database. An error message should be displayed for invalid dates.
Screenshots
Additional context Invalid dates in the database are causing downstream errors in the ETL service. Error logs from the ETL service are attached for reference. wrror_logs_invalid_date_range.txt
Developer Checklist Developer fixing the bug should fill this checklist.