Invalid dates parsed and accepted (e.g., Feb 31 becomes Mar 2)

Tags: #<Tag:0x00007efc6448ba90>
#1

When using the ‘correctFormat’ option on a date column, any combination of a valid month and a day that is valid on some months gets adapted to be a valid date instead of being marked as invalid. So, while 02-31-2016 is marked as invalid before using the ‘correctFormat’ option, with the ‘correctFormat’ option enabled, it is translated to 03/02/16. I need the date formats to be corrected, but the validations should still mark this as invalid because it isn’t a real date.

JS Fiddle with demo here: http://jsfiddle.net/u7cwrzun/
Just enter 2-31-2016 in a date field to see it get changed to 03/02/16

#2

Hi @edmund.olson-morgan
Can you create a demo for our devs to look at? I’d be very grateful.

#3

No problem. Just added a JS Fiddle with demo (http://jsfiddle.net/u7cwrzun/) into the description of the issue. Thanks!

#4

Thanks for sharing. I get the same result.
In my option it even should not convert the date to 2nd of March, what for?

I added this issue at our Github board as it’s related to basic Handsontable features. You can track it here: https://github.com/handsontable/handsontable/issues/3471

#5

Hi, I just wanted to check in on the status of this issue. When do you expect it to be addressed?

#6

Hi @edmund.olson-morgan
The best place to check for updates is currently a Github issue at https://github.com/handsontable/handsontable/issues/3471

The issue is not in the currently processed milestone 0.24.4 but as soon as it gets under assignment you’ll be able to see it’s new status.

#7