You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When marking notifications as read using @novu/js we end up in a inconsistent state for the unread indicator in the widget:
What you can see here, that there is no more indicator on the bell but one unread notification in the list.
I already discussed this issue with @jainpawan21 and he confiremd that this must be a bug. This issue is only to have something we can track the progress. Please let me know if you need any further information on this.
👟 Reproduction steps
Mark notification as read
👍 Expected behavior
Unread count and read notifications in widget should always be in sync
👎 Actual Behavior with Screenshots
See description
Novu version
Self Hosted, latest
npm version
No response
node version
No response
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
📜 Description
When marking notifications as read using @novu/js we end up in a inconsistent state for the unread indicator in the widget:
What you can see here, that there is no more indicator on the bell but one unread notification in the list.
I already discussed this issue with @jainpawan21 and he confiremd that this must be a bug. This issue is only to have something we can track the progress. Please let me know if you need any further information on this.
👟 Reproduction steps
Mark notification as read
👍 Expected behavior
Unread count and read notifications in widget should always be in sync
👎 Actual Behavior with Screenshots
See description
Novu version
Self Hosted, latest
npm version
No response
node version
No response
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Contributing Guidelines?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: