-
Notifications
You must be signed in to change notification settings - Fork 84
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
Quotes are required to validate datetime type #60
Comments
(Also suddenly getting a feeling of deja vu. I think I filed something similar to this a while ago. Hopefully not the same thing! Maybe related.) |
What version are you running this on? the latest released? It should be rather easy to track down. |
@jdandrea I think i found the reason for this. If you look here 1.5.1...unstable#diff-80ba2584958bd7cca1bb82dd943c87cfR241 (The diff between last release and HEAD you see that there is tests in there to validate just this case and i think there is a fix in there somewhere to sort out your timestamp problem. I will go through the current changes and see if i can get a new minor release out today or tomorrow and hopefully your problem should be fixed. If you want to validate it before that happens, you can test your schema against the latest commit in unstable branch. |
Thank you in advance! Yes, I'm on 1.5.1. |
@jdandrea Release will be out later today. Closing this for now. |
Thank you! Appreciate the update. |
Given the schema:
and data:
The following error is returned:
However, enclosing the date in quotes works:
Expectation: Quotes should not be required for the value to be recognized as a valid datetime type.
The text was updated successfully, but these errors were encountered: