Starting with a feature-driven folder structure can help keeping the app clean over the long run. So the project ends up in a mess of different approaches. But due to time pressure, the developers never have the chance to clean up the folder structure. It may save us some headaches in the long run.įrom my experience, many projects evolve in a similar way as described on this page. At the same time, our folder structure is simple enough to use in a project from the start. Due to the self-contained nature of the “features” it should be easy to refactor if necessary. Alan Alickovic with his awesome example project Bulletproof React suggests separating the files inside each feature by file type (as we did in the beginning).īut from my perspective, our current folder structure is sufficiently clean and descriptive. For example, the todo folder currently looks a bit messy. We could continue for a bit and clean up the folder structure within a feature. I personally am very happy with this folder structure. But at least for the moment, we removed these potential dumping grounds. We can still re-introduce them if necessary.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |