Better Folder Structure

[iammukeshm]

Feature Folders

• Interfaces
• Validators
• Exceptions
• Services

and so on.

Ultimately, DEVS can easily find out where to find which code, and to develop simple to understand solutions.

[fretje]

Just a suggestion maybe: I would refrain from putting stuff in a "type" folder if there's only one or 2 classes underneath... It's probably best to decide on a case by case basis, but If there's less than 8 to 10 classes under a feature folder, I'd rather see them all together in the root of that folder than in 6 separate type folders, especially if the names of the classes also contain the type name... It might be just me though ;-)

[iammukeshm]

@fretje I am thinking to restructure in this way.

Feature Folder ---> type

So that everyone knows what goes where. Any suggestions?

[fretje]

Same remark as before: I would concentrate on making feature and sub-feature folders, and if those features are small enough, there's even no need for that extra layer of 'type" folders. For me personally all these folders give me cognitive overload ;-)

For the Domain project specifically, there's really not that many files... Try a folder structure like this for instance:

Auditing
Catalog
Common
Dashboard
Identity
Multitenancy

and throw everything in there without subfolders... I think it's still gonna be very manageable... it's only when a project really grows that it will become apparent where things need to be split up more... and that will usually be in newly created feature-folders anyways after a project is created from this template.