3 ms·
Honest question from someone with little real world experience outside .Net: This is MVC's convention, to "Place models, views and controllers in their own fol
by loco5niner 10y ago
Honest question from someone with little real world experience outside .Net: This is MVC's convention, to "Place models, views and controllers in their own folders", and it's what I'm used to working with. Can you point me to resources outlining other methods (responding with google "XYZ" would be fine too).
- prawks 10y agoDjango's recommended project structure is one that immediately comes to mind. A project is broken down into "applications" each which have their own models, views, and controllers (among other things like forms, tests, etc.). Each "application" is an area of responsibility within the project, like payment or user management. As it's python, the 'views' module could technically be a folder with multiple files inside it, but they would all be grouped under their respective app.
- amirouche 10y agoThere several reasons to create a folder. The question is simplistic to me if the folder describe a `model' I call it model. If it describe a feature like "cart" I call it... `cart'...
- ellyagg 10y agoOrganize projects by feature: http://jaysoo.ca/2016/02/28/organizing-redux-application/ http://jaysoo.ca/2016/02/28/organizing-redux-application/
- Roboprog 10y agoThank you, thank you. THIS, exactly this.
- kentosi 10y agoI believe it's called vertical packaging. Package "employee" contains: EmployeeDto, EmployeeService, EmployeeController Package "order" contains: OrderDto, OrderService, OrderController And so on. This way logic that is closely related is kept closeby.
- macca321 10y agoA .NET take on it https://lostechies.com/jimmybogard/2015/07/02/ndc-talk-on-solid-in-slices-not-layers-video-online/ https://lostechies.com/jimmybogard/2015/07/02/ndc-talk-on-so...