mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-17 07:42:23 +00:00
The low-stock alert fired when the projected runway dropped below the user threshold (default 7 days). For a sparse cadence — a weekly injection's 7-day floor is barely one dose-interval — the warning landed with about one dose left, too late to reorder before the supply ran out. Add an optional per-medication reorder lead time plus a user-level default (0–60 days, default 10) and widen the alert trigger to max(lowStockRunwayDays, leadDays + cadenceIntervalDays), so the warning lands before the last dose for any cadence. Because the trigger is a max() over the user floor it never shrinks anyone's current threshold; a daily med with no lead keeps its prior boundary. The push body and the card notice surface concrete dates — supply runs out around <date>, reorder by <date> — with a last-dose informational state and the days/units fallback when supply data is thin. Retire the stale fixed 4-dose count threshold on the GLP-1 details endpoint and route its card lowStock flag through the same runway evaluation so the card and the daily cron agree. Surface the lead default in the low-stock settings card with progressive disclosure; a single medication can override it. Additive schema: nullable Medication.reorderLeadDays (migration 0161, no backfill) and notificationPrefs.medication.reorderLeadDays. OpenAPI regenerated.
37 lines
1.6 KiB
TypeScript
37 lines
1.6 KiB
TypeScript
import { apiSuccess } from "@/lib/api-response";
|
||
import { getReminderThresholds } from "@/lib/app-settings";
|
||
import { apiHandler, requireAuth } from "@/lib/api-handler";
|
||
import { annotate } from "@/lib/logging/context";
|
||
import { prisma } from "@/lib/db";
|
||
import { parseNotificationPrefs } from "@/lib/validations/notification-prefs";
|
||
|
||
export const dynamic = "force-dynamic";
|
||
|
||
export const GET = apiHandler(async () => {
|
||
const { user } = await requireAuth();
|
||
|
||
const thresholds = await getReminderThresholds();
|
||
|
||
// v1.16.11 — the low-stock runway threshold rides along so every
|
||
// threshold consumer reads one endpoint. Unlike `lateMinutes` /
|
||
// `missedMinutes` (operator-level singleton) this one is PER-USER:
|
||
// it lives in `notificationPrefs.medication.lowStockRunwayDays`
|
||
// (1–60 days, `null` = alert off, default 7) and is written through
|
||
// the established `PATCH /api/auth/me/notification-prefs` path.
|
||
const row = await prisma.user.findUnique({
|
||
where: { id: user.id },
|
||
select: { notificationPrefs: true },
|
||
});
|
||
const prefs = parseNotificationPrefs(row?.notificationPrefs ?? null);
|
||
const lowStockRunwayDays = prefs.medication.lowStockRunwayDays;
|
||
// v1.17.0 — the user-level reorder lead default rides along so the
|
||
// medication cards can derive the same reorder-lead-aware trigger the
|
||
// daily cron uses (per-medication overrides come from the list payload's
|
||
// own `reorderLeadDays`).
|
||
const reorderLeadDays = prefs.medication.reorderLeadDays;
|
||
|
||
annotate({ action: { name: "settings.reminder-thresholds.get" } });
|
||
|
||
return apiSuccess({ ...thresholds, lowStockRunwayDays, reorderLeadDays });
|
||
});
|