drf-spectacular VS swagger

Hi, while that is the case, same can be done with drf using drf-spectacular

I would suggest drf-spectacular instead because https://github.com/axnsan12/drf-yasg#openapi-30-note

Here is your answer: drf_spectacular

If you roll your own thing, you will probably just end up re-implementing a crappy version of something that already exists. Plus, you'll miss out on really nice utilities like this one.

Generate OpenAPI3 schema for error responses using drf-spectacular: No API is complete without proper documentation. This is work in progress (PR1 and PR2). Most of it is done, but I still need to add tests and documentation. Hopefully, that will be done over the next few week(end)s. But, if you want to get a glimpse on the expected result, here’s a screenshot of a test endpoint using swagger UI.

drf-yasg - generates schema for django application - GitHub - axnsan12/drf-yasg

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.