Suggestion: namespaced reducers / actions

Hi!

I love redux and I love reducers that filter actions by a namespace and created my own namespaced-duck-factory library because of that.

It seems that redux-toolkit could make my lib obsolete so I would love to have the option of creating state slice reducers that filter actions by a { meta: ‘namespace’ } property (for example).

If I understand it correctly it would be a little extension of createSlice() so it also emits namespaced action-creators.

Thanks for reading 😃

[soundyogi]

Sorry to comment such an old thread.

As It turns out. redux-toolkit did indeed made it unneccessary to have preconfigured slices. (I also never really needed the namespacing) Especially with the entityAdapter and immer out of the box.

So this library gave me so much joy and makes my life easier.

I even managed to introducce it to a context / hooks only codebase for a large client and it works very well so far - we use it to make redux-less redux possible (by using it with useReducer() and some middleware)

So thanks and:

Happy Christmas (well, soon-ish) 😄 @phryneas

[phryneas]

Heyo 😃

createSlice already namepaces all actions going with the slice - so an increment action on a counter slice would be of type counter/increment.

So if you were to namepace that again, I believe it would be more appropriate to namespace the type one level deeper (creating types like namespace/counter/increment) instead of using meta for that - as reducers usually decide solely by type if they’re responsible for handling an action and many established patterns (and interop with many other libraries) break if this rule is ignored.

If you wanted to do that, there’s nothing speaking against creating some kind of “higher-order-slice” like this:

function createCounterSlice(namespace: string) {
  return createSlice({
    name: `${namespace}/counter`,
    initialValue: 0,
    reducers: { increment(state){ state++; }  }
  });
}
const clickCounterSlice = createCounterSlice('click');
console.log(clickCounterSlice.action.increment()) // { type: 'click/counter/increment' }

So I think your use case should already be covered - would that work for you?

PS: I love the logo of your library - childhood memories!