0.2.52
This commit is contained in:
@@ -427,7 +427,7 @@ the alert that announced it has long since fallen out of its window. Things to p
|
||||
— unauthenticated on purpose, since a probe needing a token would report a stale session
|
||||
as a server outage.
|
||||
|
||||
**My Alerts belongs to a person, so it lives in the user picker.** A service alert is the
|
||||
**Notifications belong to a person, so they live in the user picker.** A service alert is the
|
||||
house being told something; these are one viewer's own news (a followed show returning),
|
||||
stored per user on the gateway and following them to whichever television they sign into.
|
||||
`ui/alerts/AlertsPage.kt` is the full page and the user menu in `UserSwitcherOverlay` is the
|
||||
@@ -450,6 +450,14 @@ behind it. Things to preserve:
|
||||
- **The page is stateless**, like `SignInContent` and the detail panes: `MainActivity` owns
|
||||
the list and the requests, which is what lets `AlertsPageScreenshotTest` render it (and
|
||||
the user menu carrying its badge) with no server → `build/screenshots/my-alerts/`.
|
||||
- **A cancellation is a transition, not a status read in isolation.**
|
||||
`sonarr_series_status_history` stores the first daily Sonarr reading as a quiet baseline
|
||||
and appends only changes after it; `WatchSonarrLifecycle` creates a notification for every
|
||||
known user when any show moves from continuing/upcoming to ended/deleted. Cancellation
|
||||
news is household-wide and does not depend on whether a viewer followed the show. Without
|
||||
the baseline,
|
||||
enabling the scanner would announce every show that had already ended as new news, and
|
||||
without durable history a gateway restart could announce the same change again.
|
||||
|
||||
**Search** (`ui/search/`) is a two-pane instant-search destination on the rail: a fixed
|
||||
6×6 on-screen keyboard on the left, a results grid on the right that updates as you type.
|
||||
|
||||
Reference in New Issue
Block a user