Issues with react component #185
Replies: 1 comment
-
Hi @RuslanHryn , The default BellCounter is connected to a store with id I've been able to confirm the issue regarding marking multiple categories as 'read'. I'll take it to the team. Every mark-as-read operation that doesn't include multiple categories, works as expected. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
we are currently evaluating the usage of MagicBell and found a few issues in your react component.
The bell counter is not working when no tab with all messages
For example. we have multiple categories: common, maintenance, and billing, and display them in separate tabs.
In this case, the bell counter will not be displayed at all.
To workaround this issue, we can add an additional tab to display messages from all categories:
{ id: 'all', defaultQueryParams: { categories: ['common', 'maintenance, 'billing'] } },
Seen/Read all button do not work if using tabs and categories
Example of source code
Steps to reproduce:
Actual: all messages became unread again after refreshing the page
Steps to reproduce
Actual: all messages became unread again after refreshing the page
It looks like the problem in the following requests
POST
https://api.magicbell.com/notifications/seen?categories=common%2Cmaintenance%2Cbilling
Response code 204
POST
https://api.magicbell.com/notifications/read?categories=common%2Cmaintenance%2Cbilling
Response code 204
and after the notification endpoint returns the messages without
seen_at
andread_at
fieldshttps://api.magicbell.com/notifications?categories=common%2Cmaintenance%2Cbilling&page=1
Beta Was this translation helpful? Give feedback.
All reactions