Reusable ducks?

How would you suggest making a duck that supports multiple instances?

(And by “duck”, of course I mean a reducer bundle such as the ones under src/redux/modules.)

For example, counter.js is the logic behind the “You have clicked me X times” button on the home route. What if I want three of those buttons?

I can add three instances of its reducer to the store:

export default combineReducers({
  auth,
  counterLeft: counter,
  counterCenter: counter,
  counterRight: counter,
  form,
  info,
  widgets
});

How would you hook up each CounterButton to the right property, and how would you direct the duck’s actions to the correct reducer instance?

Thanks for this repository!

[erikras]

This question intrigued me so much that I wrote a whole new library, multireducer, to handle this use case.

I’m not sure how often something like this will come in handy in a production app, but the inability to use the same simple reducer in multiple places on the Redux state tree seemed like a hole in Redux functionality that needed patching. @gaearon, could you give that library a quick glance and let me know if I’m way off base?

[gaearon]

I did look at the paginate example, but was thrown off because it duplicates action creators for each instance - for example, loadStarred and loadStargazers.

It does not “duplicate” them—you can generate them exactly the same way like you generate the reducers. I didn’t want to introduce too much indirection to examples because you often want to put business logic into action creators: for example, they may exit early based on different conditions, or do different things on success.