mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-09 13:01:00 +00:00
Marc-André Bombeck
270f33edb2
The worth-a-look rail mixed actionable items (an overdue dose, a broken sync) with observational ones (a milestone, a new ECG pointer, a tension window) that have nothing to act on beyond "seen it" — there was no way to clear them short of them expiring on their own. Add server-side dismissal scoped to the three observational kinds only: a new DismissedPriorityItem table (userId + itemKey, composite-unique), a POST /api/daily/digest/dismiss route, and a deterministic itemKey the digest builder stamps per kind (metric + reach day for a milestone, the recording's own timestamp for an ECG, the local day + part of day for a tension window) so a dismissal never bleeds into a later day's instance. The actionable kinds never carry an itemKey, so the dismiss affordance and the endpoint are both structurally unreachable for them — an itemKey not namespaced under a dismissible kind 422s before any lookup.
31 lines
1.4 KiB
SQL
31 lines
1.4 KiB
SQL
-- Server-side "dismiss / mark seen" ledger for the Today rail's OBSERVATIONAL
|
|
-- PriorityItem kinds (milestone, ecg_new_recording, tension_window). The
|
|
-- ACTIONABLE kinds (dose_window, sync_issue, preventive_care, coach_checkin)
|
|
-- never write a row here — they clear on their own once the user acts.
|
|
--
|
|
-- `item_key` is a deterministic identity for the candidate INSTANCE the
|
|
-- digest builder already computes (kind + metric + reach day for a
|
|
-- milestone, the recording's own timestamp for an ECG, the local day for a
|
|
-- tension window) — not the bare kind — so dismissing today's milestone never
|
|
-- suppresses tomorrow's.
|
|
|
|
-- CreateTable
|
|
CREATE TABLE "dismissed_priority_items" (
|
|
"id" TEXT NOT NULL,
|
|
"user_id" TEXT NOT NULL,
|
|
"item_key" TEXT NOT NULL,
|
|
"dismissed_at" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
|
|
CONSTRAINT "dismissed_priority_items_pkey" PRIMARY KEY ("id")
|
|
);
|
|
|
|
-- CreateIndex — the dismiss upsert's natural key + the digest read's
|
|
-- `userId + itemKey IN (...)` lookup.
|
|
CREATE UNIQUE INDEX "dismissed_priority_items_user_id_item_key_key"
|
|
ON "dismissed_priority_items" ("user_id", "item_key");
|
|
|
|
-- AddForeignKey — deleting a user cascades its dismissal rows away.
|
|
ALTER TABLE "dismissed_priority_items"
|
|
ADD CONSTRAINT "dismissed_priority_items_user_id_fkey"
|
|
FOREIGN KEY ("user_id") REFERENCES "users" ("id")
|
|
ON DELETE CASCADE ON UPDATE CASCADE;
|