Is this a good way to structure a project?
if not, what would be a reccomended approach?
6 Replies
I personally dislike grouping things by "what they are", instead preferring "what feature they relate to"
this is by and large an opinion-based question. But I tend to prefer something similar, where i largely separate by what role they have. So i often have Services, Integrations, Data, Controllers as my main four. @Pobiega could you elaborate a bit on your line of thinking here? im interested in hearing other approaches
I always put extensions and config in the namespaces they belong to though, instead of in an anonymous extensions namespace.
He is probably referring to something like $vsa where you group all the things needed for a feature into one folder
That is exactly what I'm talking about, yes.
seems a little complex for my 2-day project
i think i will just put everything in the same project and keep it simple
and have a repositories folder, a data folder, services folder and a results folder where i will keep all my result classes