We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
Its a very good way to add awilix to fastify but I would suggest to make the project more modular.
In my opinion, rather than having controllers , routes folder, it's better have modules and inside each module have the following structure.
It would make the project more modular
. └── modules/ ├── example/ │ ├── example.controller.js │ ├── example.route.js │ ├── example.service.js │ └── example.schema.js └── example1/ ├── example1.controller.js ├── example1.route.js ├── example1.service.js └── example1.schema.js
The text was updated successfully, but these errors were encountered:
Hey thanks for the comment ! In the future, it may be easier to split a monolith service into pieces. I will concern that
Sorry, something went wrong.
No branches or pull requests
Hi,
Its a very good way to add awilix to fastify but I would suggest to make the project more modular.
In my opinion, rather than having controllers , routes folder, it's better have modules and inside each module have the following structure.
It would make the project more modular
.
└── modules/
├── example/
│ ├── example.controller.js
│ ├── example.route.js
│ ├── example.service.js
│ └── example.schema.js
└── example1/
├── example1.controller.js
├── example1.route.js
├── example1.service.js
└── example1.schema.js
The text was updated successfully, but these errors were encountered: