Skip to content

Conversation

@hamza221
Copy link
Contributor

@hamza221 hamza221 commented Dec 1, 2025

Ho to test:

  1. checkout feat: pin favorites #12111
  2. Have favorite and non favorite messages in a mailbox
  3. toggle favorite state for one message and watch it not update pinned state
  4. cherry-pick this commit and test again

Signed-off-by: Hamza <hamzamahjoubi221@gmail.com>
@hamza221 hamza221 added the bug label Dec 1, 2025
@hamza221 hamza221 mentioned this pull request Dec 1, 2025
4 tasks
@hamza221 hamza221 changed the title fix: favority reactivity fix: favorite reactivity Dec 1, 2025
Signed-off-by: Hamza <hamzamahjoubi221@gmail.com>
Signed-off-by: Hamza <hamzamahjoubi221@gmail.com>
Copy link
Member

@ChristophWurst ChristophWurst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested and works.

In the inbox the flagged message moves as expected

If I'm not mistaken there can be cases where we introduce phantom messages with this frontend-only reordering.

Example (consiser the number behind the msg as the timestamp):

  • Flagged
    • msg 11
    • msg 10
  • Other
    • msg 27
    • msg 26
    • msg 25 (not loaded from the server yet)

^ if you unfav 11 or 10 it will go below 26. 25 will never be loaded. it's a phantom.

IMO you can't do this front-end only. We also don't do that in the priority inbox AFAIK.

@GVodyanov
Copy link
Contributor

I looked into this and yes this is an issue, but seeing as messages do get sorted into the favourite section on mailbox sync, the feature is considered ready to release by Christoph.

Therefore, seeing as this isn't considered high priority anymore, I will be unassigning myself.

@GVodyanov GVodyanov removed their assignment Dec 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: 📄 To do

Development

Successfully merging this pull request may close these issues.

4 participants