coodig-api
drf-yasg
coodig-api | drf-yasg | |
---|---|---|
1 | 8 | |
1 | 3,337 | |
- | - | |
7.4 | 1.0 | |
7 months ago | 8 days ago | |
Python | Python | |
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
coodig-api
drf-yasg
-
Swagger for Django api
I believe drf-yasg what you need. You can create a schema manually and define request and response types for your small API.
-
How can one enable the html for apis that are not apiviewsets using django rest framework?
Check this out: https://drf-yasg.readthedocs.io/en/stable/
-
Separate project vs multiple apps on a single project
There's also the caveat of having different API documentation for both the frontend solution and the API-only solution, since I don't want to expose the frontend-specific endpoints to the API-only endpoints, but I think that might just take some time playing around with swagger: https://drf-yasg.readthedocs.io/en/stable/
-
Deploying Django Rest Framework with Postgres on fly.io
Swagger and OpenAPI capabilities using drf-yasg, where you can only see endpoints and Swagger docs if you have a valid Token
- does anyone find a way to use swagger ui
-
Beautiful Hackernews UI: Working with Hackernews API in Python (Django)
The major apps are news and accounts. While the former handles almost all the physical functionalities of the system, the latter only does user stuff. The api app exposes the data for consumption. It is documented using drf-yasg, a Swagger generation tool implemented without using the schema generation provided by Django Rest Framework. The api has a token-based authentication which requires that all POST requests must provide a token to be accepted, otherwise a not too interesting response:
-
Keeping Documentation Debt At Bay & Clients Happy
Our RESTful API was actually the easiest to document, because we were able to rely on third-party libraries from the start. It was a Python Django and Django REST Framework project that leveraged the drf-yasg OpenAPI generator library to create OpenAPI and Swagger compatible documentation.
-
Documenting Django Rest Framework API
This post will go through how to document your DRF APIs using https://github.com/axnsan12/drf-yasg/ package.
What are some alternatives?
recipe-api - A recipe sharing API built using Django rest framework.
drf-spectacular - Sane and flexible OpenAPI 3 schema generation for Django REST framework.
pycentral - Aruba Central Python SDK
Django REST Swagger - Swagger Documentation Generator for Django REST Framework: deprecated
timein-api - REST API for a project management app
swagger-ui - Swagger UI is a collection of HTML, JavaScript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API.
redoc - ๐ OpenAPI/Swagger-generated API Reference Documentation
dj-rest-auth - Authentication for Django Rest Framework
drf-nested-routers - Nested Routers for Django Rest Framework
django-rest-framework - Web APIs for Django. ๐ธ
drf-flex-fields - Dynamically set fields and expand nested resources in Django REST Framework serializers.
ReDoc - ๐ OpenAPI/Swagger-generated API Reference Documentation [Moved to: https://github.com/Redocly/redoc]