Gives every notification kind its own notification and briefing card switches #81
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/notify-card-routing"
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?
Each event kind that can be a notification, a briefing card, or both now has two independent per-user switches in notification settings: notifications on or off, and briefing card on or off. Together they give notification only, card only, both, or neither. The card switch is account level. Channel choices for notifications stay as they are.
Storage stays in the existing notification preferences. The save uses the same shown-marker pattern as the channel switches, so submitting the form with every box unticked still saves as all off. Notification creation and delivery check the notification switch. The briefing builder checks the card switch after dismissal bookkeeping, so a stored dismissal survives the card being switched off and back on. Kinds with no card show No card instead of a dead switch.
New kinds in this round:
Two things to flag. The briefing deck cap moves from 12 to 14 because the new contract and camp cards pushed a dense fixture over the cap and hid the mail card. And TestBriefingFontPreloadAndFooter fails on clean main too (font 404), so that failure predates this branch.
Gate: gofmt clean, go vet clean, targeted suites pass (settings, notify routing, briefing routing). No version.txt changes.