-
Notifications
You must be signed in to change notification settings - Fork 119
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
bug(dateTime) parsing for DateTime without explicit format now consis… #379
bug(dateTime) parsing for DateTime without explicit format now consis… #379
Conversation
04be57a
to
1f1c61e
Compare
@@ -0,0 +1 @@ | |||
dateTimeProperty: 31/12/2019 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confused, shouldn't this have to be 12/31/2019 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should be. Bogged my test when I tried to make it fail. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed now.
…tent with default format Signed-off-by: Jerome Simeon <jeromesimeon@me.com>
1f1c61e
to
123f73a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Signed-off-by: Jerome Simeon <jeromesimeon@me.com>
…tent with default format
Signed-off-by: Jerome Simeon jeromesimeon@me.com
Issue #375
DateTime variables without format now are parsed exactly as if having the default
YYYY/MM/DD
format.Changes
DATE
andDateTime
rules from base parserDateTime
bindings to use the formatMM/DD/YYYY
NOFORMAT
formatted dates