state-safety-action-creator-guard

To enforce state invariants in Redux reducers, implement clamps that prevent negative values and route updates through canonical action creators. This ensures predictable state transitions and guards against invalid data during event processing.

Using action creators instead of raw dispatch calls enforces state safety by centralizing update logic. This pattern ensures canonical ActionTypes are used, making state transitions predictable and easier to unit test across your codebase.

Review PRs for state safety by verifying all state updates go through action creators, checking that reducers implement clamps for invariants, and confirming unit tests cover negative-value scenarios to guarantee predictable state transitions.

A reducer clamp is a boundary check applied during state updates to enforce invariants like money >= 0. You need clamps in state management when processing events that could reduce values below valid thresholds.

Yes, unit tests for negative-state scenarios are required. Tests should cover action creators and reducers to verify clamps are implemented correctly and invariants hold true when processing events that trigger negative values.

This state safety approach applies to codebases using reducers and action dispatch patterns, including hooks. It adjusts reducers and hooks to enforce invariants and prefer action creators for predictable state transitions.