What about directory structure?

[achtan]

Will be Mantra opinionated about directory structure?

[arunoda]

oh yes.

[arunoda]

Hope this is answered :)

[achtan]

Yes is it, sort of :)
Many developers use type-based structure:

actions/
    | articleActions.js
    | commentActions.js
components/
    | article.jsx
    | comment.jsx

imho better is feature-based structure:

comments/
    | comment.js
    | commentActions.js
articles/
    | article.jsx
    | articleActions.jsx

and I'm afraid that Mantra will use first approach and that's kind of worries me :/

[arunoda]

That's something we need to figure out first. We'll go with 1 for now.
We will have a module system, where you could keep actions, UI components and the containers in a single folder.
You can even distribute them via NPM.

But that's not coming with the initial draft. We'll have it.

[natecox]

+1 for the feature-based structure. I think it's a better way of laying out larger projects, and more in line with the react methodology of grouping feature based code together.

[achtan]

@arunoda you can maybe reopen this issue to get more opinions from people

[arunoda]

@achtan That's a good idea.

[leocavalcante]

Feature-based 👍
This reminds me about Uncle Bob's talks where he says about that architecture should reflect intent like a blueprint of a church/library, you see it and you already know what it is about. You open a source-code folder, sees post/, comment/, author/ and category/ you already knows it's about a Blog.

+1 for Feature based.

[Maxximus007]

+1 for Feature based

[markshust]

+1 I think it'll be easier to understand logic & testing flow if everything is feature-based

[adrianmcli]

+1 for Featured based.

Agreed. Feature-based is probably better for scalability. I used to use a type-based structure, but an app quickly grows in size and you end up having these huge folders filled with many many files.