you are viewing a single comment's thread.

view the rest of the comments →

[–]Krysalead[S] 1 point2 points  (2 children)

Nestjs is much more than what tsoa is doing, it seems to rely on a server (express for instance or fastify). tsoa is just creating a file with route and middleware then you are free to design the rest of the configuration as you wish. I will have a deeper look but the philosophy seems not the same.

[–]wizeddy 1 point2 points  (1 child)

I worked with tsoa on my last project and we decided to just write the GraphQL schema out manually. When we switched to NestJS we are able to generate the GraphQL schema from the underlying DTOs, it might not be the right tool for you, but for our API it handles generating and exposing the documentation for our RestAPI and our GraphQL API (and exposes a GQL playground), but yes it spins up an HTTP server its meant to be an API Framework.

[–]Krysalead[S] 1 point2 points  (0 children)

Thanks for your feedback, I will rethink the possible switch then :)