-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Create a new repo fastify/demo #1001
Comments
Imho It is already too much work to maintain the core plugins. I have the feeling that few core deps need more love but we have currently no time. It would be cooler if you first help with the other plugins before we open a demo repo. If the core plugins are all green, a demo repo on top would be no Problem. |
You mean code coverage? |
Do you have a concrete example you are willing to share or would you like to start one? |
I'd like to start a clean repo, following carefully the doc and trying to find interesting uses cases. Something basic at first, in order to gather your feedbacks and plan what to do next. But I'd like to know if you're interested before jumping in. |
Sorry @Uzlopak, I recently worked on an issue to increase test coverage on |
I believe any contribution can be of value, and this seems to provide good basics to start with |
Thanks for the proposal @metcoder95, It's not urgent so I can gradually work on this demo and looking at ongoing issues to help you with core plugins. @mcollina, are you open to the idea of an official demo repo on your side? |
+3 I would like seeing such an official demo repo using several plugins like maybe autoload, cors, env, helmet, mysql and swagger. With some routes, controllers, etc. |
When I was in the PHP ecosystem, I worked with the Symfony framework. They have created a symfony/demo repo using what they consider best practices. I found the perspective of reading the code of a web project considered optimal by the core team very useful and reassuring.
Do you think it's worth it?
If so, I'm fully committed to work on it.
I'm not sure what the theme should be, though. It seems that the main type of development in the Node ecosystem are apis.
The text was updated successfully, but these errors were encountered: