I wrote over 20 Swagger documentations before I finally learned how to do it properly. It’s frustrating that I didn’t come across your videos a year ago
We can do even better by using the cli i mean we can define the swagger as a plugin there and in this case, you will not need to add the swagger definition in the dtos and schema etc. By the way, your video quality is getting better.
Hey @mohaamiin8767, you are actually not the first person to ask the question. I might do a video on the topic. Here is a response that I've given in a previous comment; hopefully, that'll be useful to you 🙏 ---- Have you considered not using an ORM? Before adding a tool/library/layer, can you ask yourself these questions? - What is the problem I'm trying to solve? - Is that problem worth solving? - Is that problem worth solving now? (Do I have the time and budget for it) - Does the tool/library/layer I want to add introduce more complexity? If yes, is the added complexity worth it? - If you work on a team, are your team members happy with the change, are the happy to learn something new, do you have the time and budget for everybody skill up? This was my very diplomatic way of saying if you're unsure about which ORM to choose, don't use one . Plus you can always come back and add one later if you want to.
Hi, Your videos are quite engaging and it is very clear. I am really enjoying watching your videos and trying to apply same in my projects. If possible can you also include source code so it saves us lot of time. Thanks
This is horribly wrong pattern. The documentation shouldn't clutter the code like this. With so many @dectorators, the code quickly lose readability and simplicity. It also has significant performance hit while using Nestjs. The better alternative is to supply AI your code of the API and it'll generate the proper OpenAPI spec yaml/json itself.
Hey @mettle_x thanks for the feedback, do you use a dedicated AI to generate an OpenAPI spec? I would really love to try that option. You really quickly get used to decorators, and as long as you understand that they are here to add metadata and extra behaviour to the method they applied to, it becomes very natural. Is there any performance benchmark you can point us to regarding the impact of adding swagger decorators?
Hi Tech Vision, You are doing amazing in your industry. I am a designer and I have redesigned the thumbnail of your recent video. How can I contact you?
I wrote over 20 Swagger documentations before I finally learned how to do it properly. It’s frustrating that I didn’t come across your videos a year ago
Thank you so much for such a nice comment
I have seen your channel recently and your content is pretty good would be nice a tuturial for ci cd nestjs in some vps or aws
I really appreciate your videos. They are amazing. Please make videos on ReactJs and NextJs beginner to pro
Excellent as always. Thank you for your hard work.
🤜🤛
Great videos🎉
I would love to see a Nextjs with a custom NestJs backend project including Authentication and tRPC in a monorepo/turborepo ❤
Your videos are very useful. Thank you very much for your work!
We can do even better by using the cli i mean we can define the swagger as a plugin there and in this case, you will not need to add the swagger definition in the dtos and schema etc. By the way, your video quality is getting better.
Simply explain. Thank you for made a great video
NestJS also has a OpenAPI plugin so you won't have to decorate each endpoint, DTO etc... Details in the offical NestJS docs
Maybe sometimg about clusters/multi threading? :D
Thanks! I also wanted to ask which ORM you recommend for NestJS, and whether that ORM is future-proof
Hey @mohaamiin8767, you are actually not the first person to ask the question. I might do a video on the topic.
Here is a response that I've given in a previous comment; hopefully, that'll be useful to you 🙏
----
Have you considered not using an ORM?
Before adding a tool/library/layer, can you ask yourself these questions?
- What is the problem I'm trying to solve?
- Is that problem worth solving?
- Is that problem worth solving now? (Do I have the time and budget for it)
- Does the tool/library/layer I want to add introduce more complexity? If yes, is the added complexity worth it?
- If you work on a team, are your team members happy with the change, are the happy to learn something new, do you have the time and budget for everybody skill up?
This was my very diplomatic way of saying if you're unsure about which ORM to choose, don't use one . Plus you can always come back and add one later if you want to.
Hi, Your videos are quite engaging and it is very clear. I am really enjoying watching your videos and trying to apply same in my projects. If possible can you also include source code so it saves us lot of time. Thanks
I have an interceptor that transform my response,is there a way I can apply a global response type that can take in a generic for data.
Love it. Just love it. Thank you ❤
can we please get a long form video on how to implement bob c. martin's clean architecture in nestjs??? pleaseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
great video ! please provider the source codes
Amazing content, thank you!
Thank you again for this video. This one is again really helpfull. I would like to get in contact with you. How can i do that?
Do you have an business email?
I use scalar, way better
Will check it out 👍
This clutters code so much :( even tho its how it is said to do in docs)
Hi just start watching your tutorial is amazing,
Just want to know do you have any experience in java ?
Thanks for the kind feedback, Yeah I used to code in Java but that was nearly 10 years ago 😅
Great as usual!
Heyyy great to hear from you 🤜🤛
I didn’t like this approach with nexts..fastify has a better simpler approach which alllows you to build the docs from the schemas of your api
First here
🥇
This is horribly wrong pattern. The documentation shouldn't clutter the code like this. With so many @dectorators, the code quickly lose readability and simplicity. It also has significant performance hit while using Nestjs. The better alternative is to supply AI your code of the API and it'll generate the proper OpenAPI spec yaml/json itself.
Can you suggest how we can make good documentation for Nestjs Api. Please provide some good solutions for this
Link a article
Hey @mettle_x thanks for the feedback, do you use a dedicated AI to generate an OpenAPI spec? I would really love to try that option.
You really quickly get used to decorators, and as long as you understand that they are here to add metadata and extra behaviour to the method they applied to, it becomes very natural.
Is there any performance benchmark you can point us to regarding the impact of adding swagger decorators?
Hi Tech Vision,
You are doing amazing in your industry. I am a designer and I have redesigned the thumbnail of your recent video. How can I contact you?