Skip to content

Restructure the User file into two separate files (controllers and routes) #27

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

Open
petertheprofessional opened this issue Jun 30, 2022 · 3 comments
Assignees

Comments

@petertheprofessional
Copy link
Contributor

petertheprofessional commented Jun 30, 2022

To follow organizational patterns that we have learned up to this point (NVC)

@mathiasbrito-dci
Copy link
Contributor

What are your suggestions? To have subpackges for controller, routes, and models? Could the models be in one file, or do you think we need to split them also?

@petertheprofessional
Copy link
Contributor Author

I am only suggesting only splitting the User file into two separate files because the controller and router are doing two separate files. We can break down into further files if we wish but that can be further debated

@mathiasbrito-dci
Copy link
Contributor

We need to understand the advantages of separating the files, I'm in favor of it, but the current style is also a useful one. Splitting files can avoid conflicts if we have different developers working on routes, models, and controllers of the same object/concept of the system. But a system with many models can end up with a lot of files (this is the con). We could think this for the next sprint maybe since people already started working with this structure... what do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants