Feature Suggestion: setPropCaseReducer function for basic updates

[Harris-Miller]

I'm sure that this caseReducer

(state: State, action: PayloadAction<T>) => {
  state.propName = action.payload;
};

Is common enough that @reduxjs/toolkit should supply a function abstraction of it

const setPropCaseReducer = <State, Prop extends keyof State>(prop: Prop) => (state: State, action: PayloadAction<State[Prop]>) => {
  state[propName] = action.payload;
};

type UserState = {
  email: string;
};

const initialState: UserState = {
  email: ''
};

const useSlice = createSlice({
  name: 'user',
  initialState,
  reducers: {
    setEmail: setPropCaseReducer<UserState>('email')
  }
});

[EskiMojo14]

this pattern is explicitly discouraged - reducers should be modeled as events and modify as many properties as is necessary.

[Harris-Miller]

¯\_(ツ)_/¯

[markerikson]

Yeah, this is similar to the answer I gave in #2658.

We actively don't want users to be writing a bunch of reducers that are all state.fieldName = action.payload all the time.

That's not to say you should never do this - I've even written a few of these myself over in the Replay codebase.

But it's a pattern we want users to minimize, rather than one we want to encourage.