We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
At the moment, the parser only recognizes time references if:
This is implemented here:
tzbot/src/TzBot/Parser.hs
Lines 274 to 275 in 0f58a50
Line 445 in 0f58a50
Lines 339 to 340 in 0f58a50
The rationale is to avoid parsing things like "The product ID is AEH9AM" as "9AM".
However, there can be situations where a legitimate time reference is not actually preceded by a space:
>>> parseTimeRefs "How about Mike's suggestion (9am tomorrow)?" []
We should be able to parse these.
The text was updated successfully, but these errors were encountered:
Here's a real-world example:
Notice how (5 pm MSK, 4 pm CET) was incorrectly interpreted as MSK, 4 pm. The 5 pm part was ignored because it was not preceded by a whitespace.
(5 pm MSK, 4 pm CET)
MSK, 4 pm
5 pm
Sorry, something went wrong.
Yes another real-world example:
it will be at 11 AM CEST (9 AM UTC+0, 12 PM MSK)
The bot parsed UTC+0, 12 PM
UTC+0, 12 PM
No branches or pull requests
Clarification and motivation
At the moment, the parser only recognizes time references if:
This is implemented here:
tzbot/src/TzBot/Parser.hs
Lines 274 to 275 in 0f58a50
tzbot/src/TzBot/Parser.hs
Line 445 in 0f58a50
tzbot/src/TzBot/Parser.hs
Lines 339 to 340 in 0f58a50
The rationale is to avoid parsing things like "The product ID is AEH9AM" as "9AM".
However, there can be situations where a legitimate time reference is not actually preceded by a space:
We should be able to parse these.
The text was updated successfully, but these errors were encountered: