-
Notifications
You must be signed in to change notification settings - Fork 0
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
File structure #43
Comments
Creating a Note that if we do go that route, the test folder would need to be called I definitely support adding a |
I am in support of this refactoring too. I think we really need to be sure all our ducks are in a row before we do this, or we could wind up needing to do one hell of a merge. |
We can halt work on the UI for an afternoon to rework the project structure. Make sure everyone is happy and then continue. |
If we do take an afternoon to do so, we should also make sure we're compliant with eslint at the same time. |
The file structure is a mess, as we have all the test files with the components and don't separate the components out. I think it would be beneficial to organize the files a little, so that 1) newcomers won't be overwhelmed by all the files in
src/
and 2) to allow for better clarity as to how things are connectedWe could implement something like such:
project_home/
The text was updated successfully, but these errors were encountered: