date validation before setting it

[valotas]

Using an input format like DD.MM.YYYY and setting the date to something like 12.30.1980 the calendar will compute it as 12.01.0000.

Is there a way to validate the given date before using it? I would expect something like moment(input, 'DD.MM.YYYY').isValid() before computing the thing.

[bevacqua]

Can you show me the code?

[valotas]

Sure, here you are: http://jsbin.com/siyecocoja

[mlent]

Also having this problem.

It looks like this happens when the input field starts blank, and then a user provides an invalid date. If you give the input field a valid initial date, it will "revert" to the previous date if a user tries to type something invalid.

[bevacqua]

Okay, so, technically what Rome is doing isn't wrong. As you type, Rome parses 12.3 as a valid date for 12.03.0000. From 12.30 on, the date is completely invalid so it falls back to the last known valid date, 12.03.0000. If you don't want dates in the year 0000 to be valid, you should set a min date, which will make the date invalid until the user enters a date that includes a valid year as well. Another option is to take the year first, that way it'll be more obvious and natural.

This is, however, not a bug.

[valotas]

Well, it is not a bug, but it would be better to give a hook to validate given inputs.

I did not find something like that. Setting a min date is a partial solution, as I do not always know the minimum date.

If you give me a hint on where to start, I could implement it.

[bevacqua]

The problem is that:

moment('12.3', 'DD.MM.YYYY').isValid()
// <- true

moment has a strict option, but using that would be a breaking change.

moment('12.3', 'DD.MM.YYYY', true).isValid()
// <- false

moment('12.30.1980', 'DD.MM.YYYY', true).isValid()
// <- false

moment('12.03.1980', 'DD.MM.YYYY', true).isValid()
// <- true

[bevacqua]

I would create an option for strict date validation, and then make it the default in a later version.