-
Notifications
You must be signed in to change notification settings - Fork 271
feat: Allow user to control message view mode #10945
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
Conversation
97d05cd
to
2c6772c
Compare
If you receive two messages that form a thread, you will still only see one entry in your INBOX with the current approach, right? |
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.
it works as described
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.
Tested and doesn't work. It's only possible to open the latest received message of a thread. I can not open earlier ones, because they are not shown in the message list. The list is still threaded.
Correct! I was not aware we stacked messages in the list, I have already made the backed and front end changes, just need to updated some backend tests, will push the update soon. |
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.
Looks sane
Are there any plans to skip building threads if the user doesn't use them anyway?
if ($view !== null) { | ||
$view = $view === 'singleton' ? IMailSearch::VIEW_SINGLETON : IMailSearch::VIEW_THREADED; | ||
} | ||
$messages = $this->mailSearch->findMessages( |
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.
Inline the var and you have a smaller diff ✨
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.
Done, Hopefully this is what you ment
|
Fixed, took some major head scratching to find the correct code. |
Will fix lint errors on final approval |
Apologies if my communication wasn't clear from the ticket and task description (#5913 (comment)). I should have communicated this more actively. Do you see an issue with handling "dethreading" on the database level? With the latest changes we see lots of conditional logic for threaded vs non threaded views. When every message forms a thread of one, we don't need the conditional logic, do we? Building threads needs a check to be skipped with any solution. With the current state they are still built:
|
I see what you mean on the building threads part, this should now be addressed. As for the conditional logic on the front end, if I understand your comments properly, yes we do (but I might be missing something), can we discuss on Monday? |
Okay |
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.
Let's use the current approach
lib/Service/Search/SearchQuery.php
Outdated
@@ -12,6 +12,8 @@ | |||
class SearchQuery { | |||
/** @var int|null */ | |||
private $cursor; | |||
|
|||
private bool $stacked = true; |
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.
to keep terminology consistent please use threaded
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.
Done
Signed-off-by: SebastianKrupinski <[email protected]>
d09bccc
to
084cc67
Compare
Resolves: #5913
Summary
User Setting
Administrator Settings