date.parse( "3pm tomorrow" ) returns the date of tomorrow, 12:00:00 AM. about datejs

[GoogleCodeExporter]

Same thing on FF3.5.7 Win2K3.

Funny thing is, I could've sworn this was working correctly a few weeks 
ago...maybe I
wasn't looking very closely.

Original comment by [email protected] on 22 Jan 2010 at 9:55

[GoogleCodeExporter]

What is happening in the code is that the parser is processing the information 
in one loop. It is either processed as a 'set' or a 'add' function, getting 
into trouble when processing something like 'tomorrow at 5pm'. This is neither 
a 'set' nor an 'add' function, but should be split in two and processed 
separately. I've fixed this bug in a separate github repository since we where 
hitting the same issue. I solved it by allowing the 'parse' to be part of the 
chain (so now we can do things like 'Date.parse('tomorrow').parse('at 5pm')'. 
The parser itself uses this and splits the line in two, handling both separate. 
This results in the correct answers and the tests in Ruby_chronic are now green.

Original comment by [email protected] on 12 Jul 2011 at 7:51