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

Year bias... #69

Open
dickster opened this issue Mar 26, 2014 · 1 comment
Open

Year bias... #69

dickster opened this issue Mar 26, 2014 · 1 comment

Comments

@dickster
Copy link

question/misunderstanding rather than an issue.

for 01-01-22 --> year = 2022.
for 01-01-33 --> year = 1933
(in either case it could conceivably be 1922/2022 or 1933/2033)

it's nice that it does that but in come cases i want to warn the user that this year biasing is done. is there anything in API like isYearInferred() or getAlternateYearPossiblity()
or can the parser yield two different dates for ambiguous cases?

@joestelmach
Copy link
Owner

There is a timeInferred property on DateGroup, and I agree there may be a valid argument for an inference property in this case as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants