Documentation
¶
Overview ¶
Package notifications holds the viewer-scoped notifications inbox at the reserved top-level /notifications name (spec doc 02 section 1.1). The inbox is backed by the notifications domain layer: it lists the viewer's threads, newest first, with an Inbox (unread) and an All filter, both served by the same domain query the REST /notifications endpoint runs, so the page and the API never disagree about what the viewer is subscribed to. An anonymous request bounces to the sign-in form with return_to carrying the inbox, the 302 github.com answers. When the notifications service is not wired the route still exists and renders the empty-inbox blankslate.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Deps ¶
type Deps struct {
Notifications *domain.NotificationService
Repos *domain.RepoService
Render *render.Set
View *view.Builder
Logger *slog.Logger
}
Deps are the inbox handler's dependencies: the notifications domain service every list runs through, the repo service that resolves each thread's repository for its link and full name, the render set, the view builder for the shell chrome, and a logger.
Source Files