You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(data-table): surface inline-edit save failures instead of swallowing them (#2106)
A rejected inline-edit save (e.g. a 400 validation failure — an invalid status
transition) was caught with only `console.error`. Symptom: the save bar stayed
stuck, the cell kept the unsaved value, and the author got no feedback at all
(reproduced live on the showcase Studio preview: done→in_review was rejected
server-side, silently).
- saveRow / saveBatch: extract the server's reason (the ObjectStack adapter
decorates thrown errors with the parsed body on `details`) and show it in the
toolbar with an alert icon, instead of failing silently. The pending edit is
kept so the author can fix and retry.
- Tint failed row(s) destructive (`erroredRows`) so it's unambiguous which rows
didn't persist — no phantom "looks saved" state.
- Clear the error on a successful save (per-row or batch) and on cancel.
- Add `table.saveFailed` across all 10 locales.
- Tests: a failed save surfaces the reason and keeps the pending change; a
successful save shows no failure message.
Applies to both the runtime list grid and the Studio design preview (one code
path). Found while verifying the editInline work end-to-end.
Co-authored-by: Jack Zhuang <277994282+os-zhuang@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
0 commit comments