Proposal: mechanism for handling multiple actions with the same reducer. about redux-actions HOT 8 CLOSED

I've been using this feature at work via a fork of this project and it's turned out great for DRY'ing up our reducers (especially when using reducer composition). I'll see if I can contribute this feature back to the repository.

As mentioned above though, I don't see a cleaner path to doing this than the combineActions approach.

from redux-actions.

👍 I like this a lot, and it's something that has kept me from fully adopting a createReducer/handleActions abstraction in my applications.

I know this issue is fairly dead, but there is interest :)

from redux-actions.

👍 Here's some additional interest

from redux-actions.

👍

from redux-actions.

👍

from redux-actions.

thats very very useful 👍

@lukewestby is there any wip on this?
if not so, can I start working on it?

from redux-actions.

👍

I'd love to have this feature too. Should someone just submit a PR for this?

from redux-actions.

I was thinking that a conventional delimiter like | could work, but there's no obvious way for library users to join action creators (which can be used as inputs to handleActions or handleAction) since the way an action creator stores its type (via toString) seems encapsulated from the library user.

So, I think the combineActions approach seems the most reasonable.

from redux-actions.