Improve date/time parsing about remindmeofthistweet HOT 8 CLOSED

Also, something like "by 12:45 am" used in the middle of the day seems to refer to the past 12:45 instead of wrapping, even though the forwardDate option is specified.

(Edit: Solved in 788dfc3)

from remindmeofthistweet.

https://twitter.com/xchurlx/status/1132742758102425604 (Diagnosis: Chrono doesn't recognize the pattern (missing month), so the "27th" is considered as a divider for two date/times. I've disregarded this as an edge case.)

https://twitter.com/Delftsey/status/1148307327340167173?s=19 (Diagnosis: The "." between date and time makes chrono consider them as separate times. Solved in 632b275)

https://twitter.com/nytafili/status/1148306855753465857?s=19 (Diagnosis: False negative)

https://twitter.com/Dehddy_/status/1148283228119343105?s=19 (Diagnosis: The "by" between "tomorrow" and time makes chrono consider them as separate parts. Solved in 632b275)

from remindmeofthistweet.

Solved (mostly) in #11

from remindmeofthistweet.

https://twitter.com/simi_giwa/status/1150892610334199808?s=19

My guess is: two objects with time. Interesting.

from remindmeofthistweet.

https://mobile.twitter.com/triplerolex/status/1166069397385076738

from remindmeofthistweet.

For unexpected formats, you might have better luck using some AI. I've used Azure Cognitive Services successfully: https://azure.microsoft.com/en-us/overview/ they also have a free tier in some regions.

from remindmeofthistweet.

Maybe, but I think it would be faster with local parsing (plus no rate limits). I'll only switch to an API if there are significant problems

from remindmeofthistweet.

I meant this link actually: https://azure.microsoft.com/en-us/services/cognitive-services/language-understanding-intelligent-service/ but OK.

from remindmeofthistweet.