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
A read attribute on the notification resource would be helpful, with a boolean to denote read or unread status.
PFE is currently using the delivered attribute on the notification resource for the header notifications count and UI on the notifications page for read or unread status of notifications. This can be confusing when the Talk API (properly, as intended) toggles delivered from false to true when a user is emailed according to their notification email settings.
I came across this again this morning. I asked a question on Every Name Counts yesterday. Two volunteers replied overnight but their replies were marked as already read when I checked my notifications on the site today.
A
read
attribute on the notification resource would be helpful, with a boolean to denote read or unread status.PFE is currently using the
delivered
attribute on the notification resource for the header notifications count and UI on the notifications page for read or unread status of notifications. This can be confusing when the Talk API (properly, as intended) togglesdelivered
fromfalse
totrue
when a user is emailed according to their notification email settings.Please see this comment from related PFE Issue 4727 for additional information.
Notable code:
The text was updated successfully, but these errors were encountered: