-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
[NV-3037] 🐛 Bug Report: Wrong Socket Close in useUnreadCount.ts #4582
Comments
Thank you for raising this bug. Indeed you are right. |
Please assigne me |
@p-fernandez I'll open a PR for the socket one. Perhaps @krishanu7 can have this other one? These still references unseen count when they should probably be unread. |
I think it is better if you can fix both issues in the same PR as you identified them. 🙂 |
@p-fernandez just checked the code. It seems the other parts I mentioned were actually already correct, no? It's just reflecting the change after having updated unread to unseen. Please let me know if my assumption is correct. If not, I'll add more changes. Here's the PR #4590 |
📜 Description
In this hook, you're doing
socket.on(WebSocketEventEnum.UNREAD)
but you're doingsocket.off(WebSocketEventEnum.UNSEEN)
.👟 Reproduction steps
None
👍 Expected behavior
It should closes the correct socket channel.
👎 Actual Behavior with Screenshots
Novu version
0.17.0
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?
Yes
NV-3037
The text was updated successfully, but these errors were encountered: