-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Discussion] Project structure #1
Comments
I agree. I was thinking if we can have the project structure but for each feature: auth:
chat:
I think that with this structure it is more easy to refactor or work in a feature |
If we could stay away from creating folders as much as we can, that'd be great, since having deeply nested folders is painful. Having a |
I agree with @pedromassango. |
Pardon me for the late reply. I found that creating folders on a per-feature basis makes navigating around the project harder, actually. What @pedromassango proposes is fine and it's how the project was structured in the clean architecture series. Either organization is fine, it's really up to your preference. A shared "feature" is a good idea, @RollyPeres. @fabriziocacicia I'm not sure I entirely agree on this one. Developers can still work on just one feature, let's say it's "auth". No matter how the folders are structured, the developer doesn't have to venture into other features' code to write "auth" code. |
Are features completely decoupled from other features? |
We can always have |
First of all nice approach and some heavy work you did here. Secondly, I feel like a per feature structure would be really beneficial, since you'd get everything in one place. Having to navigate between folders when working on a specific feature is pretty annoying I'd say.
The text was updated successfully, but these errors were encountered: