Skip to content
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

Chrono unable to parse "2005" or "3005" #296

Open
hollowaysmith opened this issue Jul 22, 2019 · 2 comments
Open

Chrono unable to parse "2005" or "3005" #296

hollowaysmith opened this issue Jul 22, 2019 · 2 comments

Comments

@hollowaysmith
Copy link

hollowaysmith commented Jul 22, 2019

> new Date("2005")
2005-01-01T00:00:00.000Z

> chrono.parseDate("2005")
null
@gagan-bansal
Copy link

As there is no valid date. Try like

> chrono.parseDate('2005-12-01')
2005-12-01T06:30:00.000Z

@kilik52
Copy link

kilik52 commented Oct 16, 2019

The problem is that even if we want to tell chrono to recognize 2005 as year by adding a custom parser, the result will still be discarded by refiner.
So i was unable to find a way for chrono to parse 2005 at this moment.

mnvr added a commit to ente-io/ente that referenced this issue Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants