Changelog

1.5.0

• provide examples for the request/responses and view actions

1.4.0

• for headers and “other responses” you can specify a also a comma-separated list of actions and/or methods.

• request and response schema customization through the methods get_request_schema and get_response_schema respectively.

• different serializer for request and response through the methods get_request_serializer_class and get_response_serializer_class.

• fix a bug that doesn’t allow to publish specs view under versioned path.

1.3.4

• fix support for django-fsm 2.7.0

• support @schema_method for ReadOnlyField to_representation.

1.3.3

• fix views so they can be published under //.

1.3.2

• the swagger-ui view now follow same rule as the specs view regarding authentication and permissions.

• the @schema_method decorator now support the kwarg many (by default False) to tell drf-connect-docs that the returned object is an array.

• fix a bug that doesn’t collect info about default headers, responses and manual parameters.

1.3.1

• add support for custom authentication classes for schema views.

1.3.0

• support callables for @schema_method’s schema keyword arguments.

• for @schema_method’s field and serializer kwargs now can be expressed as a module dotted path.

• specs view now by default inherits authentication and permissions from DRF’s settings.

1.2.0

• add a view to serve the generated schema file.

• add an embedded swagger-ui to help developers to document the API.

• add a feature to generate the schema file on application startup.

• remove regex patterns from generated file.

• improve the manual parameter management.

• refactoring of app settings.

1.1.1

• fix a bug with path resolution.

• add a waring disclaimer in the API description with the specs generation timestamp.

1.1.0

• request now have resolver_match: this change improve introspection in some circumstances.

• merge_schemas now support schemas over http(s).

1.0.0

• First public release!