fix(price): remove baseprice detection, use directional price match
baseprice > price was wrongly treated as "quantity discount" — it's just GoMag's promotional price. Now: price_gomag <= pret_roa is always OK, only flag when GoMag charges MORE than ROA. Reset cached price_match at startup for re-evaluation. Fix dashboard dot color for mismatches. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
7
TODOS.md
7
TODOS.md
@@ -27,10 +27,3 @@
|
||||
**Effort:** S (human: ~2h / CC: ~10min)
|
||||
**Context:** TIER 2 matched county+city without street, reusing VFP-era addresses with wrong streets. After removal (2026-04-06), new imports create correct addresses. Old wrong addresses stay. Could identify them by: address has id_loc but no linked order rows, and was last modified before 2026-04-06.
|
||||
**Depends on:** TIER 2 removal deployed and verified.
|
||||
|
||||
## P3: Extract match-column badge styles to CSS classes
|
||||
**What:** Replace inline styles on Kit and Disc. badges (in shared.js) with CSS classes (e.g., `.match-badge-kit`, `.match-badge-disc`).
|
||||
**Why:** Currently both badges use identical inline `style="background:var(--X-light);color:var(--X-text);font-size:10px;padding:2px 6px"`. If a 3rd badge type appears, inline styles become a maintenance burden.
|
||||
**Effort:** XS (human: ~30min / CC: ~5min)
|
||||
**Context:** Low priority. Two inline-styled badges is fine. Trigger: when a 3rd badge type is needed in the price match column.
|
||||
**Depends on:** Quantity discount feature shipped.
|
||||
|
||||
Reference in New Issue
Block a user