-
Notifications
You must be signed in to change notification settings - Fork 166
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
Request: Support for DD/MM/YYYY #28
Comments
Let me play around and see what that would look like. Since dd/mm vs mm/dd are ambiguous for this state-machine, I think it would have to be declarative (different function name). |
Still working on this. Have finished refactor as precursor and will create an API to prefer DD/MM when ambigous. |
Internationally, dd/mm is way more common than mm/dd, right? Afaik, only the USA uses mm/dd, while the entire rest of the world uses mm/dd.. |
According to WP, DMY is by far the most used format, then YMD, distantly followed by the remainder including MDY. What about using the system timezone to set a default format? |
The current implementation of |
I'm currently stuck on this one too.. What about exposing the |
All the cases where the You can use my fork while it is waiting for a merge |
Test cases now validates the following is true: * Fixed araddon#91 * Fixed araddon#28 (previous commits already addresses these issues, these tests ensure that these issues remain fixed)
Hello!
I noticed dateparse doesn't currently have support for UK based dates, is this within scope?
Flipped examples from mm/dd/yyyy:
The text was updated successfully, but these errors were encountered: