Prevent dates from being adjusted by a User's timezones

When a date is passed as 2018-01-01 to the component as a string via the value prop, it gets converted to a JavaScript Date object.

The user’s timezone reflects during this conversion.

A user in New York will see 2017-12-31 on his datepicker component rather than 2018-01-01 because GMT-4

[mykeels]

Oh, nice! It’s been open for a few months now @charliekassel … It would be really helpful if it’s merged.

[mykeels]

@charliekassel In my use case, I am binding the value to the datepicker component from a PHP blade template, not using it within another vue component where I’d be able to manipulate a date before passing it as a prop, so I have to use a string.

One way to get around this is to convert the date-string to reflect the user’s timezone, basically suffix it with 00:00:00 GMT-4

However, a prop that tells the datepicker to ignore the time part of the date (or lack thereof) would be helpful.

If it’s a datepicker, it makes sense that it should be able to be concerned with just dates and not their time values.