-
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
Refactor Components and Pages #31
Comments
Bumping this - I think we should prioritize this first. |
@gwwatkin some ideas from my last discussion with @Keelando: Splitting
We would have Also we should limit the usage of |
These are all great ideas and definitely desirable features. Also agree with the file structure. Only thing I can suggest is |
I think refactoring is important, but would like to mention that I think it's important to keep an eye on what creates value for the project. Some times it's easy to get caught up in making things look pretty in the code and loose connection with what matters for the user |
What I propose is that we conclude the current PR and implement the remaining changes along the way while moving forward on other UI issues. When refactoring a lot before making new changes there is risk of doing and undoing work - we want to be strategic an refactor things as they improve our productivity |
@gwwatkin agree that we should implement those changes alongside with working on UI stuffs. The main goal here is to have enough separation so that it is easier to manage and update later on. |
Just on the progress for this issue: I think the current separation that we are having is good, the last component I would split is |
Components are nicely formatted now, starting from: |
Many of the components will need to be refactored into smaller chunks and individual components for readability and easier editing and debugging.
For example, the component called LatticeView.tsx is very big and can be separated into smaller components.
This will probably occur "soon-ish" after more web UI functionality is brought in.
The text was updated successfully, but these errors were encountered: