In-app notification infrastructure #92
Labels
No labels
bug
devops
duplicate
enhancement
good first issue
next major release
next minor release
question
testing
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#93 Feed staleness detection and alerts}
lvl0/fedi-feed-router
#94 Publishing failure notifications}
lvl0/fedi-feed-router
#95 Platform credential health check}
lvl0/fedi-feed-router
Reference: lvl0/fedi-feed-router#92
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Build the notification system that other features (#82) can hook into.
Context
Split from #82. Before we can alert on feed staleness, publish failures, or credential issues, we need the plumbing: a notification model, storage, and a UI component to display them.
Tasks
Notifiableservice or trait for dispatching notifications from anywhere in the codebase