feat: Allow user to control message view mode

[SebastianKrupinski]

Resolves: #5913

Summary

• Adds the ability for a user to control message viewing mode (Threaded View or Singleton View)
• Adds the ability for a administrator to preset default message viewing mode (Threaded View or Singleton View)

User Setting

Administrator Settinig

[ChristophWurst]

If you receive two messages that form a thread, you will still only see one entry in your INBOX with the current approach, right?

[GretaD]

before

after

[GretaD]

it works as described

[ChristophWurst]

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.

[SebastianKrupinski]

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.

[SebastianKrupinski]

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.

Corrected, message are no longer stacked in message list.

[ChristophWurst]

Looks sane

Are there any plans to skip building threads if the user doesn't use them anyway?

[ChristophWurst]

Suggested change

	* @param string $sort returns messages in requested order ('newest' or 'oldest')
	* @param IMailSearcH::sort_* $sort

[SebastianKrupinski]

We can't use IMailSearcH::sort_* here the UI sends 'newest' or 'oldest' and the value of IMailSearch::ORDER_* is 'DESC' and 'ASC'

[ChristophWurst]

And this can't be streamlined?

[SebastianKrupinski]

This was existing code for the most part, the only change to the sort was that the UI now sends the sort order vs the controller pulling the value from the database every time.

I didn't want to refactor sort as it was out of scope for this PR and would make the review more difficult.

I can address this in a follow-up if you want, or do you want it as part of this PR?