You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Part of #31 — Settings & preferences parity — most of PATCH /api/user/update is unreachable from Android
The web's bell tray shows a configurable number of notifications (notificationTrayLimit).
Android's notifications feed uses a hard-coded page size and the push-poll caps its tray group
independently.
Expose the preference and have both the in-app notifications list and the system-tray grouping
respect it.
Tests: PATCH round-trip; list honours the limit.
Filed from the parity review of feature/parity-wip @ 14d7795 against interlinedlist.com (OpenAPI /api/openapi.json, 233 paths) and the public help centre.
Implemented in the PR above (branch issue/35-notification-tray-limit). Closing here — review and any follow-up happens on the PR.
Placement and range came from the docs: the web files this under View preferences, not under a notifications group (/help/settings lists it beside Messages per page, and its Notifications section points back at it), and the valid range is 10–40, default 20 — stated on /help/settings and corroborated by /help/api/notifications ("clamped to 10–40") and the live GET /api/user value.
Both consumers now honour it, which was the substance of the issue: the in-app list stops using a hard-coded page size, and the system-tray grouping drops its independent MAX_INDIVIDUAL = 5 cap in favour of the account's limit.
One behaviour change to be aware of: a batch of six notifications now posts six individually where it used to collapse into a summary. That is the intent, but worth knowing before it surprises anyone.
Crossing the module boundary needed a second narrow accessor in :core:network alongside #19's — so this adds another reader to the ownership tangle tracked in #104.
Activity
PATCH /api/user/updateis unreachable from Android #31Adron commentedon Sep 16, 2026
Implemented in the PR above (branch
issue/35-notification-tray-limit). Closing here — review and any follow-up happens on the PR.Placement and range came from the docs: the web files this under View preferences, not under a notifications group (
/help/settingslists it beside Messages per page, and its Notifications section points back at it), and the valid range is 10–40, default 20 — stated on/help/settingsand corroborated by/help/api/notifications("clamped to 10–40") and the liveGET /api/uservalue.Both consumers now honour it, which was the substance of the issue: the in-app list stops using a hard-coded page size, and the system-tray grouping drops its independent
MAX_INDIVIDUAL = 5cap in favour of the account's limit.One behaviour change to be aware of: a batch of six notifications now posts six individually where it used to collapse into a summary. That is the intent, but worth knowing before it surprises anyone.
Crossing the module boundary needed a second narrow accessor in
:core:networkalongside #19's — so this adds another reader to the ownership tangle tracked in #104.merge: #35 notification tray limit (PR)