-
Notifications
You must be signed in to change notification settings - Fork 533
Pikaday field: Invalid date #59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Could you make a fiddle with this issue? |
Found more things:
So, even when the format is good or with an empty EDIT: When Moment.js is loaded, no more problem. Is Moment.js required for Pikaday? |
They say:
|
I know, but try to remove moment.js from the dev test files and use Pikaday to select a date. You will get "Invalid date". This may not be our fault, because I don't see where we use it without importing it first. |
For quick solution please add the momentjs to pikaday as dependencies in the documentation. If I have more time, I will try to find the exact problem. |
I edited the doc and pointed to this issue |
Maybe it is fixed in #118 and momentjs removed and pikaday working. |
When I use a pikaday field with no special options, I get "Invalid date" in the field.
I can see the good value for a fraction of a second but then it get replaced by this message.
This problem don't appear with the dev environment, and I suspect it has something to do with Moment.js (or the lack of it to be precise).
I experimented a bit with
format
, but nothing change that.For now I will send a PR which don't add any default values (except
field
) in pikadayOptions.The text was updated successfully, but these errors were encountered: