-
-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
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
feat: Assign message to ad-hoc group with matching name and members (#5385) #5779
Conversation
6888326
to
c532f4c
Compare
8a6fa11
to
6b0bff1
Compare
6b0bff1
to
6bd9681
Compare
6bd9681
to
683c681
Compare
5991a16
to
363aa23
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be nice to also have a test where a message arrives that does not match the member list, otherwise complex SQL query is not tested and could be just a subject match.
363aa23
to
a7aaef2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have a migration 120 now, so needs a rebase, but otherwise LGTM.
…5385) This should fix ad-hoc groups splitting when messages are fetched out of order from different folders or otherwise reordered, or some messages are missing so that the messages reference chain is broken, or a member was removed from the thread and readded later, etc. Even if this way two different threads are merged, it looks acceptable, having many threads with the same name/subject and members isn't a common use case.
a7aaef2
to
e94af72
Compare
Fix #5385