Description
Feature Description
Right now, when clicking on pin inside read notification list, the notification will occur in both read and unread, with a read option in both read and unread list. And similar thing happens if pin is clicked in unread list. Maybe it is better to improve the logic by adding an unpin state.
-
Initial state: notification inside unread with pin and read options.
For example,
-
If the notification is pinned inside unread, only unpin option is available.
-
If the notification is then unpinned, back to initial state.
-
Similar logic for pin/unpin inside unread.
-
If a notification is pinned inside unread, click on read all will not move it to read (must unpin it first).
To implement this, we might need to add a NotificationStatusUnPinned to backend and adjust frontend logic.
And might need to separate status pin/unpin and read/unread into two variables to pass to frontend (instead of just status)
Screenshots
No response