state-actions

Redux actions for saga-driven state management are defined as plain-object action creators and upper-SNAKE type constants, enforcing three-phase async action triples like <OP>_<ENTITY>, <OP>_<ENTITY>_SUCCESS, and <OP>_<ENTITY>_ERROR for deterministic dispatch patterns.

The three-phase async action triple pattern in Redux saga generates three distinct action types per CRUD operation: the initial request, a success response, and an error response, ensuring every asynchronous entity slice update follows a deterministic lifecycle.

Redux Toolkit is not used; this approach enforces hand-written action creators and plain-object Redux actions without RTK to ensure deterministic dispatch patterns for saga-driven slice-level state management.

The best way to structure CRUD operations for entity slices in Redux is by co-locating upper-case type constants and hand-written action creators within each slice, applying three-phase async action triples for every operation.

You do not need Redux Toolkit; this approach explicitly avoids RTK by using hand-written plain-object action creators and upper-SNAKE type constants to manage slice-level state for redux-saga.

Synchronous operations alongside async CRUD verbs are dispatched by defining additional plain-object action creators and type constants within the same entity slice, maintaining co-located definitions for straightforward reuse and testing.