vuejs-datepicker
vuejs-datepicker copied to clipboard
Fix typeable dates with custom format (non-US)
As we were having problems in our project with typeable dates, we did this modification to make custom (non-US) dates parseable for Date.Parse.
We have added function, based on Kooiinc's generic method to parse dates with different formats, to convert dates with custom format to generic format that can be parsed.
Coverage remained the same at 100.0% when pulling fe9d5f02727e2c2abd3ec6dd32c185b23dc052cb on barbosaalr:master into de0fc75fe6f6572eebf47f94da20716ab7690cff on charliekassel:master.
Hello, I'm struggling from the same issue. Is this fix in npm already?
Hello, I'm struggling from the same issue. Is this fix in npm already?
Nope, not yet...
I'd love to see this PR accepted!
@charliekassel This PR is a life saver. Could you please merge it?
@charliekassel could you look at this pr, would be nice to know if it will get merged or not?
Is it already merged?
@barbosaalr This PR cover case when format
option is a function?
@tdmitriiv Maybe a good idea is to implement something like that:
https://bootstrap-datepicker.readthedocs.io/en/latest/options.html#format
... Or, only allow format
options as string, not function.
This PR fixes most of the problems, but I needed one more thing: I want my date to be only a month & a year (MM/yyyy format) This doesn't solve this as the day is necessary with this PR.
What I did was to add:
if (ymd[2] == 0) ymd[2] = "01";
just before var timezone = ...
in the parseableDate
method.
Now I can type "01/2019" in the input.
Hi guys, what can we do, to make the PR done as fast as possible? Ty
Btw. this won't work inside safari because it can't parse the timezone.
Hello! Is there a quick way to implement this changes? Should I just edit the files in the node installation directly? Thank you!
Just came across this issue, any update for this?
any news?????? @charliekassel please 🙏
Facing this issue as well! Please approve!
Any news on this yet?! Could really use with this merge
I have the same issue.
I have same issue too, Has this bug been fixed yet? I type in 1/6/2020 to mean 1st June 2020. But the pop-up locks to 6th Jan 2020.
This won't be fixed. The author didn't commit anything since 24.07.2020 and just replied to really dumb criticism and a request to take over the project. The issues an PR's are pilling up. You should move to another repo, there are forks of this repo that fix a lot of issues