Hacker News new | past | comments | ask | show | jobs | submit login

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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: