-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve folder structure #303
Comments
I do agree that we must reorganize a bit. Maybe more in the scope of #34. I'm not a big fan of the I don't see the benefit of having:
over:
In case I need a component file, I just hit |
Make sense, maybe we could take out |
What I see as a benefit is that if you are working on I do not use myself |
Separating pages sounds good to me. Even though we only have one. |
I agree with both of you. I think this will make the project structure more readable. |
Summary 💡
As the project grows, the
components
folder is getting bigger and bigger, I suggest a different approach to structure it where every component is in its own folder allowing the set of components to grow and follow clearly.Also adding a
pages
folder for every view on the router. And leavingApp
andRouter
outside.Examples 🌈
Where
Preview.js
is the actual component andindex
just export it to do a clean import from the outside.Motivation 🔦
Improve the maintainability of the project
cc/ @smeijer
The text was updated successfully, but these errors were encountered: