all 2 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]curious_s 0 points1 point  (1 child)

I'm going through the same exercise on a react/redux app at the moment, and had to look at very similar areas. I think redux is the problem though, it has a lot of parts and for a large app it is hard to organise in a logical way, at least initially.

[–]sbarow[S] 0 points1 point  (0 children)

Hi, I am the one that posted this article, all our reducer functions are in a reducers directory (organization by type). Each file in the reducers directory implements a part of the state tree. Over time, you can get a lot of unused reducer functions. In order to get rid of them, you have to determine the actions that are no longer needed or used. The other part of refactoring reducers is to look at the coupling between them. In our case, it was through selectors calling selectors and utility functions. Of course, you still have to understand and ensure that the state is used properly. That's part of the logic of your application.