Issue with Validation in the New Datepicker

[SigurdEileras]

Hi!

First of all, the new datepicker looks great!

However, we encountered an issue with validation that allows the user to enter an illegal state, which wasn’t possible before.

Previously, we used the “Min Date” and “Max Date” settings in the datepicker to define the allowed date range. This worked well because it prevented users from selecting invalid dates by making dates outside the range disabled.

With the new feature that allows users to manually enter dates via the keyboard, they can now input values outside the defined range. This resulted in an issue where users were able to enter invalid dates.

We have implemented additional validation to handle this, and everything is now working fine.

However, I thik that the datepicker should, by default, show an error state if the user enters a date that is outside the defined min/max range.

[Olav]

Hello, and thank you for your feedback!

We agree that more “out-of-the-box” validation on the date picker, along with our other input components, would be good. However, the behaviour must be consistent across components and ideally also connected with relevant logic (e.g. updating and persisting to the database).

I have registered your request in a larger discussion on a more robust and comprehensive data validation concept in Create.