swagger-core VS drf-spectacular

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

JAX-RS is a java implementation of the OpenAPI Specification. - GitHub - swagger-api/swagger-core

Now Swagger UI is configured and we can start documenting our API. Inside UrlController, above every endpoint, we can use @ApiOperation annotation to add description. Depending on your needs you can use some other annotations.

Here is an example from Swagger APIs GitHub:

Im mostly in C# land nowadays, but this seems to be the java version. I’m not sure it is as deeply integrated, as I think Java has a few popular server frameworks.

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