Notifications Bell

Azure-portal notifications parity: a notifications button on the dock with an unread count, one toast queue, and a panel of what has happened recently. It renders two kinds of entry, and the difference between them is the whole design:

• Delivered — a row the server wrote for this user through the one notification pipeline (notifications). It reached every device that was subscribed, it survives the reload, and it is paged in like any other list.
• Local — feedback about what this tab just did: a mutation error, a save conflict, an export that finished here. Nothing on another device could act on it and nothing needs it after the reload, so it is never written down.

Both render through one AppNotification shape, so the panel and the toast never branch on where an entry came from. Only the store knows, and only where it has to: dismissing a delivered entry is a mutation, dismissing a local one is a filter.

Model

AppNotification (client model): id, severity (NotificationSeverity), title, body, path, createdAt, isRead, action?.

severity is taken straight off the notifications column, so the stored value and the rendered one cannot drift, and its values are the library's status tokens — a severity is handed to UiToast as its status without a translation table.

path is the in-app route the row opens, and it is what a delivered notification carries instead of a button: the whole row is the link. action is the local half's affordance — an isSingleUse action (undo-style mutations, e.g. the delete toast's Restore) is consumed on success by consumeNotificationAction, stripping the button while keeping the entry as history, because a second fire from the panel would target state the first fire already changed. Repeatable actions (navigation links, Copy public link) stay clickable.

Local sources (fired from useResourceStore and the /all list dialogs) are the feedback the server has no business repeating:

• save conflict (stale contentVersion) → warning with Refresh action (resource page parity)
• any mutation error → error severity with the message
• CSV export completed/truncated, and the file exports that produce a local artifact

Resource operations — published, unpublished, duplicated, deleted, restored, purged — are both: the acting tab shows its toast synchronously with its undo action, and the same operation is published so the owner's other devices hear about it. One wording, ResourceOperationTitleMap, is what keeps the two from drifting. An operation that turned out to be a no-op — an unpublish of a resource nothing was published for — publishes nothing at all, since a push reporting a state change that never happened is worse than silence.

Flow

flowchart TD
  LOCAL["This tab's own action<br/>error · save conflict · export"] -->|createNotification| ST
  PUSH["Delivered push"] --> SW["service worker postMessage"]
  SW -->|type reaches the bell| RE["re-read page 1"]
  RE --> ST["store/notification"]
  OPEN["Panel opened / dock mounted"] --> RE
  ST --> PANEL["bell panel — merged, newest first<br/>StyledWaypoint pages the delivered half"]
  ST --> BADGE["unread count on the trigger + PWA icon badge"]
  ST --> SNACK["toast queue (~5s, errors persist)"]
  PANEL -->|closed| READ["updateNotificationsReadStatus"]

The service worker has always posted every delivered push to each open tab before showing the OS notification; the tab end of that wire is plugins/pushNotification.client.ts. It re-reads rather than rendering the payload it was handed — the row the Function wrote is the one the panel dismisses and marks read, so adopting the wire copy would put an entry in the list with an id the server would not recognise. Pushes whose type never asked for the bell are ignored there, which is what stops a query per chat message received.

UI

• Bell (AppNotificationBell, on the dock, authed sessions): the unread count sits on its trigger, and the trigger opens a UiPopover panel — newest first, severity icon, relative time, per-item dismiss, "Dismiss all". Closing the panel marks everything read. The delivered half is cursor-paginated, with a StyledWaypoint at the foot of the list paging the next page in. Empty state: "No notifications".
• Toasts (AppNotificationToast): one UiToast in the app's toast stack rendering the store's queue head (~5s, dismissible, held while hovered); errors persist until dismissed. One queue, never ad-hoc toasts beside it.
• G N opens the panel (global search chords).
• App icon badge: the same unread count is mirrored onto the installed PWA's icon through the Badging API, so an install that is not in the foreground still shows what is waiting. Best-effort — the write is feature-detected and its rejection is logged, never surfaced. It is now the honest count rather than the tab's guess: a push delivered while the app was closed is a row, and the next load counts it.

Key files

Notes

• The delivered half is bounded by retention rather than by the session (notifications); a durable audit trail is still the activity log's job (activity log).
• The store no-ops local notifications on the server (checkIsServer) so SSR renders never enqueue toasts.