DRY & KISS Principles

How can the DRY principle be applied to improve this Redux action creators implementation?

export const fetchUserStart = () => ({
  type: 'FETCH_USER_START'
});

export const fetchUserSuccess = (data) => ({
  type: 'FETCH_USER_SUCCESS',
  payload: data
});

export const fetchUserError = (error) => ({
  type: 'FETCH_USER_ERROR',
  payload: error
});

export const fetchProductStart = () => ({
  type: 'FETCH_PRODUCT_START'
});

export const fetchProductSuccess = (data) => ({
  type: 'FETCH_PRODUCT_SUCCESS',
  payload: data
});

export const fetchProductError = (error) => ({
  type: 'FETCH_PRODUCT_ERROR',
  payload: error
});

Rename the action types
Use different payload structures
Create a factory function for action creators
This code violates DRY by duplicating the action creator pattern for different entities. A better approach would be to create a factory function: const createAsyncActions = (entity) => { const uppercase = entity.toUpperCase(); return { start: () => ({ type: `FETCH_${uppercase}_START` }), success: (data) => ({ type: `FETCH_${uppercase}_SUCCESS`, payload: data }), error: (error) => ({ type: `FETCH_${uppercase}_ERROR`, payload: error }) }; }; const userActions = createAsyncActions('user'); const productActions = createAsyncActions('product'); // Usage: dispatch(userActions.start()); dispatch(productActions.success(data)); This approach: 1. Eliminates action creator duplication 2. Makes adding new entity actions easier 3. Ensures consistency across action creators 4. Reduces the chance of typos in action types
Combine all actions into one

Next Question (12/20)