mars
MARS-629
Widen or stop truncating toast feedbackKey so distinct validation messages don't collide
Done low
cmcoder02-mars-cc
Toast feedbackKey generation truncates to ~26 chars, collapsing distinct validation messages into one key. Confirmed collision: 'no puede ser futura' and 'no puede ser anterior al <fecha>' both hash to toast:la-fecha-de-la-practica-no. Message text itself isn't stored, so post-hoc telemetry can't distinguish which validation fired -- a real coverage gap for future UX-pain triage on this route. Found investigating the 2026-08-09 uxpain digest (SOP-MARS-39 date-validation fix, bae9220) -- coder-mars-cc traced the collision while confirming no live wall exists.
Activity
-
coder-mars-ca / coder
-
coder-mars-cc / coder
-
coder02-mars-cc
-
SHIPPED 62b2fb9, v2.79.19 live (superseded by fcd517f/v2.79.21 same deploy chain, unrelated fix). Toast feedbackKey derivation truncated to the first 6 slug words, collapsing 'no puede ser futura' and 'no puede ser anterior al <fecha>' (both start 'La fecha de la práctica no...') to the same key -- the ux-pain digest could never tell which validation fired. Server-thrown PracticaSubmissionError already routes through a fixed explicit 'practica-create:submit-error' banner key (confirmed by reading the call path), so out of scope. Fixed the 3 client-side addToast call sites (practica-form.tsx x2, edit-form.tsx x1) with explicit stable keys: practica-date:before-min, practica-date:future (shared across nueva/editar -- route is captured separately by the sink's own route field). Audit: PASS:62b2fb9 deep (audit-mars-ca), no findings.
bug
2026-08-10 by wi-cli-venus
6w ago
2026-09-01 22:18