-
Notifications
You must be signed in to change notification settings - Fork 47
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
Implement MVC Folder Structure and Schema for Carbonops Backend #22
Comments
Hey @Nishitbaria thank you for the issue.We are planning on changing the existing ER Diagram a bit.As soon as that is done,we will assign this issue to you :) |
@Nishitbaria Assigned.Take reference from the ER Diagram in PR #76 |
Till tomorrow I will Create @shreya024 |
@Nishitbaria Any updates? |
@shreya024 I Have Created Pull Request you can review it : #97 |
I want to work on this issue |
Assigned! Go ahead |
Reopening as not yet completed. @Nishitbaria Don't close issues |
Description:
I would like to propose the implementation of an MVC (Model-View-Controller) folder structure and the creation of a schema for the Carbonops project's backend. The current project lacks a standardized organization of files and folders, which hampers code maintainability and scalability. Additionally, there is a need for a well-defined schema to ensure efficient data management and retrieval.
Objective:
The objective of this issue is to establish an organized folder structure following the MVC architectural pattern and create a schema for the Carbonops backend. These enhancements will enhance code modularity, readability, and the overall maintainability of the project. Additionally, the schema will provide a structured framework for managing and querying
Benefits:
By implementing an MVC folder structure and creating a schema for the Carbonops backend, the project will gain the following benefits:
Improved Code Organization: The MVC folder structure will promote a modular and organized codebase, enhancing code readability and maintainability.
Separation of Concerns: Clear separation of models, views, and controllers will facilitate better code management and future enhancements.
Scalability: The organized structure will allow for easier integration of new features and components, enabling the project to scale effectively.
Efficient Data Management: The schema will provide a structured framework for storing and querying environmental data, ensuring optimal data management and retrieval.
The text was updated successfully, but these errors were encountered: