3.0 KiB
Django REST framework 3.3
The 3.3 release marks the final work in the Kickstarter funded series. We'd like to offer a final resounding thank you to all our wonderful sponsors and supporters.
The amount of work that has been achieved as a direct result of the funding is immense. We've added a huge amounts of new functionality, resolved nearly 2,000 tickets, and redesigned & refined large parts of the project.
In order to continue
Release notes
Significant new functionality in the 3.3 release includes:
- Filters presented as HTML controls in the browsable API.
- A forms API, allowing serializers to be rendered as HTML forms.
- Django 1.9 support.
- A
JSONField
serializer field, corresponding to Django 1.9's PostgresJSONField
model field. - Browsable API support via AJAX, rather than server side request overloading.
Example of the new filter controls
Supported versions
This release drops support for Django 1.5 and 1.6. Django 1.7, 1.8 or 1.9 are now required.
This brings our supported versions into line with Django's currently supported versions
Deprecations
The AJAX based support for the browsable API means that there are a number of internal cleanups in the request
class. For the vast majority of developers this should largely remain transparent:
- To support form based
PUT
andDELETE
, or to support form content types such as JSON, you should now use the [AJAX forms][ajax-forms] javascript library. This replaces the previous 'method and content type overloading' that required significant internal complexity to the request class. - The
accept
query parameter is no longer supported by the default content negotiation class. If you require it then you'll need to use a custom content negotiation class. - The custom
HTTP_X_HTTP_METHOD_OVERRIDE
header is no longer supported by default. If you require it then you'll need to use custom middleware.
The following pagination view attributes and settings have been moved into attributes on the pagination class since 3.1. Their usage was formerly deprecated, and has now been removed entirely, in line with the deprecation policy.
view.paginate_by
- Usepaginator.page_size
instead.view.page_query_param
- Usepaginator.page_query_param
instead.view.paginate_by_param
- Usepaginator.page_size_query_param
instead.view.max_paginate_by
- Usepaginator.max_page_size
instead.settings.PAGINATE_BY
- Usepaginator.page_size
instead.settings.PAGINATE_BY_PARAM
- Usepaginator.page_size_query_param
instead.settings.MAX_PAGINATE_BY
- Usepaginator.max_page_size
instead.