humansignal-drf-yasg
Advanced tools
Automated generation of real Swagger/OpenAPI 2.0 schemas from Django Rest Framework code.
.. role:: python(code) :language: python
######################################## drf-yasg - Yet another Swagger generator ########################################
|actions| |nbsp| |codecov| |nbsp| |rtd-badge| |nbsp| |pypi-version| |nbsp| |gitter|
Generate real Swagger/OpenAPI 2.0 specifications from a Django Rest Framework API.
Compatible with
Only the latest patch version of each major.minor series of Python, Django and Django REST Framework is supported.
Only the latest version of drf-yasg is supported. Support of old versions is dropped immediately with the release of a new version. Please do not create issues before upgrading to the latest release available at the time. Regression reports are accepted and will be resolved with a new release as quickly as possible. Removed features will usually go through a deprecation cycle of a few minor releases.
Resources:
Sources <https://github.com/axnsan12/drf-yasg>_Documentation <https://drf-yasg.readthedocs.io>_Changelog <https://drf-yasg.readthedocs.io/en/stable/changelog.html>_Live demo <https://drf-yasg-demo.herokuapp.com>_Discussion <https://app.gitter.im/#/room/#drf-yasg:gitter.im>_|heroku-button|
OpenAPI 3.0 note
If you are looking to add Swagger/OpenAPI support to a new project you might want to take a look at
drf-spectacular <https://github.com/tfranzel/drf-spectacular>_, which is an actively maintained new library that
shares most of the goals of this project, while working with OpenAPI 3.0 schemas.
OpenAPI 3.0 provides a lot more flexibility than 2.0 in the types of API that can be described.
drf-yasg is unlikely to soon, if ever, get support for OpenAPI 3.0.
Features
swagger-ui <https://github.com/swagger-api/swagger-ui>_ and
redoc <https://github.com/Rebilly/ReDoc>_ for viewing the generated documentationswagger-spec-validator <https://github.com/Yelp/swagger_spec_validator>_URLPathVersioning and NamespaceVersioning; other DRF
or custom versioning schemes are not currently supported.. figure:: https://raw.githubusercontent.com/axnsan12/drf-yasg/1.0.2/screenshots/redoc-nested-response.png :width: 100% :figwidth: image :alt: redoc screenshot
Fully nested request and response schemas.
.. figure:: https://raw.githubusercontent.com/axnsan12/drf-yasg/1.0.2/screenshots/swagger-ui-list.png :width: 100% :figwidth: image :alt: swagger-ui screenshot
Choose between redoc and swagger-ui.
.. figure:: https://raw.githubusercontent.com/axnsan12/drf-yasg/1.0.2/screenshots/swagger-ui-models.png :width: 100% :figwidth: image :alt: model definitions screenshot
Real Model definitions.
Table of contents
.. contents:: :depth: 4
Usage
The preferred installation method is directly from pypi:
.. code:: console
pip install --upgrade drf-yasg
Additionally, if you want to use the built-in validation mechanisms (see 4. Validation_), you need to install
some extra requirements:
.. code:: console
pip install --upgrade drf-yasg[validation]
.. _readme-quickstart:
In settings.py:
.. code:: python
INSTALLED_APPS = [ ... 'django.contrib.staticfiles', # required for serving swagger ui's css/js files 'drf_yasg', ... ]
In urls.py:
.. code:: python
... from django.urls import re_path from rest_framework import permissions from drf_yasg.views import get_schema_view from drf_yasg import openapi
...
schema_view = get_schema_view( openapi.Info( title="Snippets API", default_version='v1', description="Test description", terms_of_service="https://www.google.com/policies/terms/", contact=openapi.Contact(email="contact@snippets.local"), license=openapi.License(name="BSD License"), ), public=True, permission_classes=(permissions.AllowAny,), )
urlpatterns = [ path('swagger/', schema_view.without_ui(cache_timeout=0), name='schema-json'), path('swagger/', schema_view.with_ui('swagger', cache_timeout=0), name='schema-swagger-ui'), path('redoc/', schema_view.with_ui('redoc', cache_timeout=0), name='schema-redoc'), ... ]
This exposes 4 endpoints:
/swagger.json/swagger.yaml/swagger//redoc/get_schema_view parametersinfo - Swagger API Info object; if omitted, defaults to DEFAULT_INFOurl - API base url; if left blank will be deduced from the location the view is served atpatterns - passed to SchemaGeneratorurlconf - passed to SchemaGeneratorpublic - if False, includes only endpoints the current user has access tovalidators - a list of validator names to apply on the generated schema; only ssv is currently supportedgenerator_class - schema generator class to use; should be a subclass of OpenAPISchemaGeneratorauthentication_classes - authentication classes for the schema view itselfpermission_classes - permission classes for the schema view itselfSchemaView optionsSchemaView.with_ui(renderer, cache_timeout, cache_kwargs) - get a view instance using the
specified UI renderer; one of swagger, redocSchemaView.without_ui(cache_timeout, cache_kwargs) - get a view instance with no UI renderer;
same as as_cached_view with no kwargsSchemaView.as_cached_view(cache_timeout, cache_kwargs, **initkwargs) - same as as_view,
but with optional cachingas_view as usualAll of the first 3 methods take two optional arguments, cache_timeout and cache_kwargs; if present,
these are passed on to Django’s :python:cached_page decorator in order to enable caching on the resulting view.
See 3. Caching_.
SWAGGER_SETTINGS and REDOC_SETTINGSAdditionally, you can include some more settings in your settings.py file.
See https://drf-yasg.readthedocs.io/en/stable/settings.html for details.
Since the schema does not usually change during the lifetime of the django process, there is out of the box support for caching the schema view in-memory, with some sane defaults:
cache_page <https://docs.djangoproject.com/en/1.11/topics/cache/#the-per-view-cache>__
decorator, using the default Django cache backend, can be changed using the cache_kwargs argumentCookie and Authorization HTTP headers to enable filtering of visible endpoints
according to the authentication credentials of each user; note that this means that every user accessing the schema
will have a separate schema cached in memory.Given the numerous methods to manually customize the generated schema, it makes sense to validate the result to ensure
it still conforms to OpenAPI 2.0. To this end, validation is provided at the generation point using python swagger
libraries, and can be activated by passing :python:validators=['ssv'] to get_schema_view; if the generated
schema is not valid, a :python:SwaggerValidationError is raised by the handling codec.
Warning: This internal validation can slow down your server. Caching can mitigate the speed impact of validation.
The provided validation will catch syntactic errors, but more subtle violations of the spec might slip by them. To ensure compatibility with code generation tools, it is recommended to also employ one or more of the following methods:
swagger-ui validation badgeOnline ^^^^^^
If your schema is publicly accessible, swagger-ui will automatically validate it against the official swagger
online validator and display the result in the bottom-right validation badge.
Offline ^^^^^^^
If your schema is not accessible from the internet, you can run a local copy of
swagger-validator <https://hub.docker.com/r/swaggerapi/swagger-validator/>_ and set the VALIDATOR_URL accordingly:
.. code:: python
SWAGGER_SETTINGS = {
...
'VALIDATOR_URL': 'http://localhost:8189',
...
}
.. code:: console
$ docker run --name swagger-validator -d -p 8189:8080 --add-host test.local:10.0.75.1 swaggerapi/swagger-validator
84dabd52ba967c32ae6b660934fa6a429ca6bc9e594d56e822a858b57039c8a2
$ curl http://localhost:8189/debug?url=http://test.local:8002/swagger/?format=openapi
{}
swagger-clihttps://www.npmjs.com/package/swagger-cli
.. code:: console
$ npm install -g swagger-cli
[...]
$ swagger-cli validate http://test.local:8002/swagger.yaml
http://test.local:8002/swagger.yaml is valid
editor.swagger.io <https://editor.swagger.io/>__Importing the generated spec into https://editor.swagger.io/ will automatically trigger validation on it. This method is currently the only way to get both syntactic and semantic validation on your specification. The other validators only provide JSON schema-level validation, but miss things like duplicate operation names, improper content types, etc
You can use the specification outputted by this library together with
swagger-codegen <https://github.com/swagger-api/swagger-codegen>_ to generate client code in your language of choice:
.. code:: console
$ docker run --rm -v ${PWD}:/local swaggerapi/swagger-codegen-cli generate -i /local/tests/reference.yaml -l javascript -o /local/.codegen/js
See the GitHub page linked above for more details.
.. _readme-testproj:
For additional usage examples, you can take a look at the test project in the testproj directory:
.. code:: console
$ git clone https://github.com/axnsan12/drf-yasg.git $ cd drf-yasg $ virtualenv venv $ source venv/bin/activate (venv) $ cd testproj (venv) $ python -m pip install --upgrade pip setuptools (venv) $ pip install --upgrade -r requirements.txt (venv) $ python manage.py migrate (venv) $ python manage.py runserver (venv) $ firefox localhost:8000/swagger/
Third-party integrations
Integration with djangorestframework-camel-case <https://github.com/vbabiy/djangorestframework-camel-case>_ is
provided out of the box - if you have djangorestframework-camel-case installed and your APIView uses
CamelCaseJSONParser or CamelCaseJSONRenderer, all property names will be converted to camelCase by default.
Integration with djangorestframework-recursive <https://github.com/heywbj/django-rest-framework-recursive>_ is
provided out of the box - if you have djangorestframework-recursive installed.
.. |actions| image:: https://img.shields.io/github/actions/workflow/status/axnsan12/drf-yasg/review.yml?branch=master :target: https://github.com/axnsan12/drf-yasg/actions :alt: GitHub Workflow Status
.. |codecov| image:: https://img.shields.io/codecov/c/github/axnsan12/drf-yasg/master.svg :target: https://codecov.io/gh/axnsan12/drf-yasg :alt: Codecov
.. |pypi-version| image:: https://img.shields.io/pypi/v/drf-yasg.svg :target: https://pypi.org/project/drf-yasg/ :alt: PyPI
.. |gitter| image:: https://badges.gitter.im/drf-yasg.svg :target: https://app.gitter.im/#/room/#drf-yasg:gitter.im :alt: Gitter
.. |rtd-badge| image:: https://img.shields.io/readthedocs/drf-yasg.svg :target: https://drf-yasg.readthedocs.io/ :alt: ReadTheDocs
.. |heroku-button| image:: https://www.herokucdn.com/deploy/button.svg :target: https://heroku.com/deploy?template=https://github.com/axnsan12/drf-yasg :alt: Heroku deploy button
.. |nbsp| unicode:: 0xA0 :trim:
Integration with drf-extra-fields <https://github.com/Hipo/drf-extra-fields>_ has a problem with Base64 fields.
The drf-yasg will generate Base64 file or image fields as Readonly and not required. Here is a workaround code
for display the Base64 fields correctly.
.. code:: python
class PDFBase64FileField(Base64FileField): ALLOWED_TYPES = ['pdf']
class Meta:
swagger_schema_fields = {
'type': 'string',
'title': 'File Content',
'description': 'Content of the file base64 encoded',
'read_only': False # <-- FIX
}
def get_file_extension(self, filename, decoded_file):
try:
PyPDF2.PdfFileReader(io.BytesIO(decoded_file))
except PyPDF2.utils.PdfReadError as e:
logger.warning(e)
else:
return 'pdf'
FAQs
Automated generation of real Swagger/OpenAPI 2.0 schemas from Django Rest Framework code.
We found that humansignal-drf-yasg demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.