Make dashboard event toasts persistent
This commit is contained in:
1 parent
4798385d8b
commit
c75e71f26e
4 files changed
+91
-14
No files matched your search
+1
-1
@@ -63,7 +63,7 @@ Rules:
|
||||
- Duplicate/replayed events must be harmless.
|
||||
- A disconnected stream marks data stale but does not blank useful cached content.
|
||||
- Invalid event payloads are contained and repaired with a snapshot refresh.
|
||||
- User-triggered outcomes may create toasts; durable/history-worthy events also appear in the notification center/activity views.
|
||||
- The notification centre retains useful lifecycle history, including successful syncs. Sticky toasts are reserved for inbound replies/media and attention-worthy failures or runtime/account states; they remain visible until the operator dismisses them.
|
||||
- Raw technical logs belong in Operations, not as general user notifications.
|
||||
|
||||
## Authentication and privacy
|
||||
|
||||
Reference in new issue
Block a user