You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the dot format is currently supported for MM.DD.YYYY, this format does not set the ambiguousMMDD flag. This leads to issues mainly in fixes for #28 (such as #89), where ambiguousMMDD needs to be set.
The way I see it, ambiguousMMDD needs to be set for all ambiguous date formats (regardless the separator).
(FWIW, I'm pretty sure the dot separator is mostly used in DD.MM.YY[YY] formats anyway.)
The text was updated successfully, but these errors were encountered:
skius
changed the title
Better support for dot-format (e.g. 12.1.2009) with ambiguousMMDD
Better support for dot-format (e.g. 13.1.2009) with ambiguousMMDD
Aug 25, 2019
Test cases now validates the following is true:
* Fixedaraddon#91
* Fixedaraddon#28
(previous commits already addresses these issues, these tests ensure
that these issues remain fixed)
While the dot format is currently supported for
MM.DD.YYYY
, this format does not set theambiguousMMDD
flag. This leads to issues mainly in fixes for #28 (such as #89), whereambiguousMMDD
needs to be set.The way I see it,
ambiguousMMDD
needs to be set for all ambiguous date formats (regardless the separator).(FWIW, I'm pretty sure the dot separator is mostly used in
DD.MM.YY[YY]
formats anyway.)The text was updated successfully, but these errors were encountered: