Looking for opinions. I am in discussion with someone who would like to restructure phoenix project file structure so that model, view, controller, and tests will be all in one folder per named “feature” (let’s say “blog”) I am looking for feedback on what the tradeoffs would be for doing this. T…

Have a look in this topic: Discussion about domain-orientated folder structures in Phoenix

Has this person considered code that must be reused between two or more features? Then their idea kind of falls apart.

[image] dimitarvp: Has this person considered code that must be reused between two or more features? Controller / view code isn’t really this way though. I definitely agree with you that "model" code definitely doesn’t belong to a specific controller. However for controller / view stuff there…

I don’t disagree but let’s take this to the extreme: should each feature have a copy of the root layout code then? The stance described in OP seems too extremist and narrow-minded to me. Partially applied it is valuable but I’ve rarely seen people advocate for such things in an moderate manner. It’…

The way being proposed is indeed all the model, view, controller as described FWIW

In practice, it’s never about the extremes though. As there is a ‘data’ App and a separate ‘web’ AppWeb both styles can be used together. If we look at how the phx generator creates the data app, we see vertical slicing as far as I can remember. Except for migrations which are all in one folder*. I…

I would not favor an all-in-one approach with models next to views, as having both an data app and web app makes a good boundary. So there I draw a line: The data app is meant for handling data requests, the web app for handling web requests. Easy distinction :slight_smile:. It also allows me to ha…

[image] Fractal — A react app structure for infinite scale | HackerNoon After having worked with React and flux (Redux) with over 8 significant projects (100+ screens each), we learned a few things about React apps. Although being designed for React, you can …

[image] samrose: I am looking for feedback on what the tradeoffs would be for doing this. The argument for it is that “everything you need to find for the feature would be in one folder. This should be easier for everyone to find and use these files”. But are there fundamental reasons not to re…

Custom restructuring Phoenix Framework tradeoffs question

Questions & Help Questions

BartOtten December 15, 2021, 9:20pm 10

Although being designed for React, you can find value information about vertical slicing in there.