fix: check for valid date in frontend

[fmartingr]

Summary

Changes the onChange function for date files and resets the field in the date set up is invalid.

Tried adding a HTMLInput.setCustomValidity method but our form does now follow that flow it seems, hence opted for not allowing the user to have an invalid input set in the field (which should not happen very frequently).

Fixes #111

[wiggin77]

@fmartingr an update to CI was just merged. Update this PR from master and it should be passing.

[wiggin77]

LGTM 👍

[AayushChaudhary0001]

@fmartingr I have tested this PR and still I am to reproduce the actual issue, please check it thorugh the screenshots below. The date which does not even exist is getting saved and the end date shown as result is never, which would result in never ending process.

[fmartingr]

I can't seem to reproduce this. Can you record a video?

Screen.Recording.2024-10-02.at.15.41.52.mov

[wiggin77]

I can't seem to reproduce this. Can you record a video?

@AayushChaudhary0001

[AayushChaudhary0001]

@fmartingr Please check the issue in this video:-

date_validation.mp4

[fmartingr]

I have been digging a bit more about this, and I'm not sure it's worth fixing for invalid dates.

Essentially, an input type date does not store the value if the date is an invalid date 1, so the code can't check easily what's on the input when a full invalid date has been entered, since the value is going to be empty.

Adding to that, we allow empty values in that field, so the submit event is valid when we enter an invalid date.

I'm not sure this is going to happen that much, so I'm not sure it's worth dedicating more time to it.

What I'm not sure on is how to handle from a UX perspective that 1% of the time that is going to happen.

cc: @wiggin77

[wiggin77]

@fmartingr let's defer this.