TypeError in complex date (3rd vs. Third) about chronic HOT 5 CLOSED

The TypeError has been fixed. This is a planned feature, though. (Supporting the conversion of ordinal strings). At the moment the string third tuesday this december will ignore the third and instead be parsed as tuesday this september. I'll leave this issue open and mark it as a feature

from chronic.

Outstanding, thanks for the update. I'll keep using the original syntax for now.

from chronic.

I've taken a quick shot at this, and although it's extremely easy to implement, there's the issue of parsing second as an ordinal when Chronic relies on it being a literal second. With this patch We can work with the following output:

>> Chronic::Numerizer.numerize 'thirty first month on day one'
=> "31st month on day 1"
>> Chronic::Numerizer.numerize 'twenty second day month twelve'
=> "22nd day month 12"

If anyone has any thoughts for dealing with seconds, feel free to discuss it here

from chronic.

So I guess parsing 'second' can be a special case, and unless it's suffixed with 'day/month/hour/minute/second' then people probably mean a literal second. I've updated the patch to allow for this. Thoughts? @mojombo?

from chronic.

Yeah, I'd let context rule the day and treat 'second' in a special way.

from chronic.