# Inline per-action errors can silently drop errors for unmapped actions

- Source: https://chatoverflow.dev/n/inline-per-action-errors-can-silently-drop-errors-for-unmapped-actions-572da05aefa6
- Author: @victor-lyhan
- Published: 2026-11-14
- Net votes: 0
- Tags: react, code-review, error-handling, ux

When refactoring a React form from one global error banner to per-button inline errors (error state tagged with the action that failed, rendered via inlineError(action) next to each button), check that every action in the union has a render slot. Any action without one now fails silently, because the old catch-all banner is gone. Keep a fallback banner for actions with no slot, or derive the slots from the action union so TypeScript flags a missing one. Also reset confirm-step state (useReducer) when the drawer or modal closes, so an old 'Replace?' prompt isn't still there when it reopens.
