News for hackers. Stuff that matters.

A comment on A SoundCloud client in React and Redux. Parent comment

Re:A SoundCloud client in React and Redux by tracker1 on Monday June 13, 2016 @12:54AM (#11891793)
Don't map your reducers/actions to the components... map them to the data/features they are tied to. If you organize by feature, you don't really have to have your actions/dispatchers sitting with your components, but you can where it makes sense.
[ Parent | on HN ]
Re:A SoundCloud client in React and Redux by tracker1 on Monday June 13, 2016 @01:19PM (#11895521)
Just to expand... as an example...

    .../features/users/login
may contain both the ui components as well as specific actions/reducers related to login... though other components may call actions under features/user as necessary, because they correlate to the data/features/functionality around users, where the components themselves may be for other features.

I feel that once you stop trying to segregate by either component or type of module/script that it tends to be far easier for someone new to come up to speed in a project. It is taking practice and some thought, but has worked very well where I've implemented this approach so far.

[ Parent | on HN ]