feat(orders): a fifth verdict, 'bad', between ok and never again
ci / lint-test (push) Successful in 47s

The jump from "OK" to "Never again" is too big and most
disappointments live in the gap (user, 2026-07-28) — so a merely poor
meal either flattered itself as OK or got blacklisted.

Only 'never' raises the warning on a future order. A blacklist that fires
for every mediocre delivery is one nobody reads, so 'bad' records the
disappointment without triggering the alarm. Both set order_again = false
— you would not choose either again — and that split between "would I
order it" and "warn me about it" is the point of the extra level.

Migration widens the CHECK; nothing is removed, so no existing row needs
mapping.
This commit is contained in:
2026-07-28 19:12:26 +10:00
parent 82f751cbf4
commit d458228625
8 changed files with 62 additions and 14 deletions
+3 -1
View File
@@ -33,6 +33,7 @@ const RATING_LABEL: Record<OrderRating, string> = {
loved: "Loved it",
liked: "Liked it",
ok: "OK",
bad: "Bad",
never: "Never again",
};
@@ -40,10 +41,11 @@ const RATING_STYLE: Record<OrderRating, string> = {
loved: "border-emerald-600 bg-emerald-950 text-emerald-300",
liked: "border-emerald-800 bg-emerald-950/50 text-emerald-400",
ok: "border-zinc-600 bg-zinc-800 text-zinc-300",
bad: "border-amber-800 bg-amber-950 text-amber-300",
never: "border-red-800 bg-red-950 text-red-300",
};
const RATING_ORDER: OrderRating[] = ["loved", "liked", "ok", "never"];
const RATING_ORDER: OrderRating[] = ["loved", "liked", "ok", "bad", "never"];
/**
* The receipt behind a delivery order: what was actually bought, where it went,