Is there a point to the params? about redux-auth HOT 1 OPEN

Another options is to just have a LOGIN_ACTION (or something) action (and get rid of all the rest), which just takes the params from the action and puts them in app state. Then just have the actions define the isAuthenticated value, etc. This would remove 3/4 of the case statements and only have one const needed for all login actions. I don't see any gains from all of the extra code and frankly, when I first looked at this as an example of redux it made me think I'd traveled back in time with how tedious it is to do very simple tasks and if it takes all of that just for login, my apps would be huge to extrapolate that pattern for everything they do.

Just do this for the reducer.

const { type, ...rest } = action;
switch (type) {
    case LOGIN_ACTION:
      return Object.assign({}, state, rest)
    default:
      return state
  }

Then have functions like this where the params are actually read:

export function receiveLogin(user) {
  return {
    type: LOGIN_ACTION,
    isAuthenticated:true,
    isFetching: false,
    user
  }
}

export function logout() {
  return {
    type: LOGIN_ACTION,
    isAuthenticated:false,
    isFetching:false,
    user:null
  }
}

I don't see the use for the way it's done in this repo other than making more work for devs. I still feel like the React ecosystem has a long way to go with some of this to make it quick and terse to set up complex interactions let alone simple ones like this.

from redux-auth.