springfox VS swagger

The only issue I saw on this is that controllers get a lot more cluttered. See an example.

Examples include Swagger-Core, SpringFox, NSwag / Swashbuckle, Swagger-express / HAPI-Swagger, Django-REST-Swagger / Flask-RESTplus, etc.

From a casual Google search - short answer, yes. Longer answer, see the link.

If Java and Spring, you can use SpringFox: write unit tests and get generated API docs as a bonus.

It seems that there might be some other configuration as the error traces back to springfox.io.

Teams that use spring can easily create specs by using Spring Fox https://github.com/springfox/springfox

Yeah the API is very similar but they serve different purposes as you mention here. It looks like there's been some discussion about aligning them since other people have had a similar observation.

1. openapi is not defined. https://github.com/nestjs/swagger/issues/1450

The repository for every optional NestJS package that has decorators seems to consistently put them in /lib/decorators. For example, here are the NestJS Swagger decorators.

NestJS provides a dedicated module which allows generating OpenAPI (Swagger) - Github - nestjs/swagger

Thanks to the system of extensions, Ditsmod applications are more expressive and with less code. For example, if you compare OpenAPI modules written in Ditsmod and NestJS, the Ditsmod module is 3.5 times smaller in the number of lines of code or the number of files.