Currently it is possible to enter a date of 55/27/2023 and not get any invalid date message (as it fulfills the date format, presumably). When we try to check and parse the value ourselves onAction, the value does not appear to be an incorrect date as it has been changed through the built in Bryntum validation to a valid (but unintended) date (in this example, it was changed to 24/04/2025).
What is the best way to amend / add our own validation on top of the built-in Bryntum date validation that occurs on input to fix this type of issue?
Thanks Tasnim. Please can you also confirm whether it is possible to supply two (or further additional) date formats for parsing the date? I can see in the source there is a fallbackFormat option that is tried after the format, but when I try to pass that value in the component it does not change anything as I don't think it's part of the editable config.
The problem that is occurring is that if the date cannot be parsed using the format (e.g. DD/MM/YYYY, but the user enters DD/MM/YY) the date is parsed in U.S. time (i.e. it makes it MM/DD/YYYY) through the built in validation (before we get a chance to validate ourselves onAction).
There is no milestone set yet, so this means in won't be resolved in nearest releases, so I cannot provide any estimations now, we need to wait a bit when project management will assign a milestone.
You can subscribe on ticket updates to be notified when status is changed.
Thanks. I understand it's now going to be deal with in the next release. I have also noticed that when I try to supply validateOnInput when using the DateField as a component, this does not seem to work. It continues to validate on input and when debugging, the DateField attrs have 'true' for validateOnInput.