-
Notifications
You must be signed in to change notification settings - Fork 295
fix: favorite reactivity #12112
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
fix: favorite reactivity #12112
Conversation
Signed-off-by: Hamza <[email protected]>
Signed-off-by: Hamza <[email protected]>
Signed-off-by: Hamza <[email protected]>
ChristophWurst
left a comment
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 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.
|
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. |
|
I'm closing this issue as discussed. |
Ho to test: