-
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
Componentize views/admin folder #353
Comments
@KarinePistili @jvJUCA I would like to work on this issue. Can you please assign me this issue? By fixing this issue, It also helps me in getting a better understand of entire codebase before making a proposal for GSOC . |
And a thing to discuss I am thinking to move the components to the components folder instead componentize in a single file. It helps in better organizing and reusuability of components. @KarinePistili @jvJUCA What are your thoughts on this ? Glad to work under your guidance. |
@jvJUCA I think it's a valid approach and makes sense |
Hello, This approach not only aligns with our goals for modularity and maintainability but also enhances the reusability of our components across the application. By encapsulating logic and styles within dedicated components, we can significantly improve the project's overall code quality and ease of maintenance. I plan to undertake this task with careful consideration of the current codebase's structure and needs, ensuring that each component is designed with reusability and maintainability in mind. I will also document the changes thoroughly and create individual pull requests for each component to facilitate a smooth review process. I'm eager to contribute to this important aspect of the project and would appreciate the opportunity to be assigned to this issue. I'm ready to discuss my proposed approach further and collaborate with the team to make this enhancement a success. Thank you for considering my proposal. |
Ok, assigned @asr2003! |
@jvJUCA Any thoughts on this? |
Dear @asr2003, Thank you for suggesting this adjustment. Currently, our project structure already includes a components folder. Within this folder, we've organized our components into organisms, molecules, and atoms, representing large, medium, and small components, respectively. This hierarchical organization has been serving us well in terms of maintaining clarity and facilitating component reusability. Best regards, |
@jvJUCA I need a suggestion our project lacks the CI/CD pipeline support. Implementing CI/CD brings automation to testing, builds and deployments. This leads to faster and more reliable development cycles, consistent and error-resistant codebase of RUXAILAB. |
Hello! @asr2003 , have you worked on this? I don't remember seeing the PR, so I'm a little confused if this was already done or is a WIP. |
Yes, It's in WIP. Currently I have exams and will complete in next 3 days. Will start remaining work and submit PR in the weekend :) |
Feature Description 📝
I propose to componentize the views/admin folder in our project. Currently, the views are contained in a single file and to improve code organization and maintainability, I suggest breaking it down into smaller, reusable components of files:
Motivation 🌟
By componentizing the views folder, we can achieve the following benefits:
Expected Behavior 🤔
The expected behavior is to have separate Vue.js components for each view in the views folder. Each component should encapsulate the logic and styles related to its specific view.
Additional Information ℹ️
Will make a PRs for every file componentized as discussed above for better review and organized
Thank you for considering this feature request! 🙌
The text was updated successfully, but these errors were encountered: