-
Notifications
You must be signed in to change notification settings - Fork 17
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 not extracted #24
Comments
A little help? I still haven't been able to get Nickel to parse years - it detects the day of the month and returns the year as a message. Not sure what might be causing this issue or how to fix it. |
Sorry, it's rather difficult to fix individual issues in nickel at the If your example is a real one, and you're just parsing dates with no |
Came up with a (very) quick and dirty workaround for the time being that works for my use case but has some obvious problems.
|
Recently updated the codebase for my app which uses nickel and I am running into an issue where the year is not identified as an occurence, and the current year (2014) or the upcoming year (2015) is used instead by default, depending on the date:
example:
n = Nickel.parse("October 28, 1969.")
n.inspect
results in the following output:
date: message: "1969", occurrences: [#Occurrence type: single, start_date: "20141028"]
The text was updated successfully, but these errors were encountered: