Open
Conversation
YuriRomanowski
added a commit
that referenced
this pull request
Feb 24, 2023
Problem: Sometimes, context of a time reference can be spread over one sentence, several different sentences or even several different messages. Solution: Parse contexts alone, remind them and apply to context-free time references when encountered; track a context during thread evolution.
b390131 to
ec5c7ca
Compare
2dcf198 to
461920b
Compare
Problem: when a user writes "10am-11am UTC ...", context is not shared between times, and second time can be skipped because every time should go after a space. Solution: Parse time references that are grouped via hyphen, slash, "and", "or" sharing their context: date ref, location ref, am/pm.
461920b to
148360b
Compare
YuriRomanowski
added a commit
that referenced
this pull request
Feb 24, 2023
Problem: Sometimes, context of a time reference can be spread over one sentence, several different sentences or even several different messages. Solution: Parse contexts alone, remind them and apply to context-free time references when encountered; track a context during thread evolution.
ec5c7ca to
9d9bfde
Compare
YuriRomanowski
added a commit
that referenced
this pull request
Feb 24, 2023
Problem: Sometimes, context of a time reference can be spread over one sentence, several different sentences or even several different messages. Solution: Parse contexts alone, remind them and apply to context-free time references when encountered; track a context during thread evolution.
9d9bfde to
e32b0bf
Compare
Contributor
Author
YuriRomanowski
commented
Feb 24, 2023
| managed $ withTzCacheDefault cCacheReportDialog | ||
| -- auto-acknowledge received messages | ||
|
|
||
| let defaultConversationStateCachingTime = hour 12 |
Contributor
Author
There was a problem hiding this comment.
This ideally should be in the config
YuriRomanowski
commented
Feb 24, 2023
| Cache.insert getMessageThreadId (msgId, newState) convStateCache | ||
| asks bsMessageCache >>= Cache.insert msgId (timeRefs, conversationState) | ||
|
|
||
| withNonEmptyTimeRefs timeRefs $ \neTimeRefs -> do |
Contributor
Author
There was a problem hiding this comment.
It seems that we will eventually rewrite this logic using some abstracting technique and write some tests, it gets a bit tricky as more internal state is kept.
Problem: Sometimes, context of a time reference can be spread over one sentence, several different sentences or even several different messages. Solution: Parse contexts alone, remind them and apply to context-free time references when encountered; track a context during thread evolution.
e32b0bf to
aa1eb6f
Compare
e3cc9f3 to
fff943d
Compare
369fbef to
4756b9b
Compare
Base automatically changed from
YuriRomanowski/#79-add-support-for-hyphenated-intervals
to
main
August 21, 2023 15:03
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Description
Problem: Sometimes, context of a time reference can be spread over one sentence, several different sentences or even several different messages.
Solution: Parse contexts alone, remind them and apply to context-free time references when encountered; track a context during thread evolution.
Related issue(s)
Part of #16
✅ Checklist for your Pull Request
Related changes (conditional)
Tests
silently reappearing again.
Documentation
Stylistic guide (mandatory)