Year-only iso date string is parsed incorrectly

[kanongil]

Context

• node version: 8.1.4
• joi version: 10.6.0
• environment (node, browser): node
• used with (hapi, standalone, ...): standalone
• any other relevant information:

What are you trying to achieve or the steps to reproduce ?

Joi.date().iso().validate('2013').value.toISOString();

Which result you had ?

'1970-01-01T00:00:02.013Z'

What did you expect ?

Same output as new Date('2013').toISOString():

'2013-01-01T00:00:00.000Z'

As far as I can tell, it unexpectedly parses it as a timestamp value.

[DavidTPate]

Yeah, that seems to be the case.

I think it is operating as expected, there's nothing there for it to use to determine whether the value is the number of milliseconds or a date. The closest thing to it is the the value happens to be a 4 digit number, but that would just be an assumption that it isn't a milliseconds value.

Did you have something in mind to address this? As I see it right now, I believe it is working as expected.

[nlindley]

In the example, iso() is specified. Wouldn’t that imply the value isn’t intended to be milliseconds?

[Marsup]

That's a good point @nlindley.

[lock]

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.