Release history and notes¶
Sequence based identifiers are used for versioning (schema follows below):
It’s always safe to upgrade within the same minor version (for example, from 0.3 to 0.3.4).
Minor version changes might be backwards incompatible. Read the release notes carefully before upgrading (for example, when upgrading from 0.3.4 to 0.4).
All backwards incompatible changes are mentioned in this document.
Tested against Django 3.1 and 3.2.
Tested against Python 3.9 and 3.10.
Tested against Django REST Framework 3.12.
Drop Python 2.x support.
Drop Python 3.5 support.
Drop Django < 2.2 support.
Drop Django REST Framework < 3.9 support.
Tested against Django 3.0.
Tested against Python 3.8.
Tested against Django REST Framework 3.11.
Tested against Django 2.1 and Django 2.2.
Tested against Python 3.7.
Dropping support for Python 3.4.
Upgrade test suite.
Temporary remove PyPy from tox (because of failing tests).
Make it possible to order by two (or more fields) at once, using the
Fixes in docs.
Fixes in docs.
OrderingFilter, which makes it possible to specify mapping (ordering option -> ORM field) for making more developer friendly ordering options in the API. An example of such could be a
Usermodel. In case if we want to order by
ProfileViewSet, instead of ordering on
user__emailwe could order just on
Update example project (and the tests that are dependant on the example project) to work with Django 2.0.
Fix issue #1 with non-required nested serializer fields.
Made tests DRY.
Tested against various Django REST framework versions (>=3.5.0,<=3.6.3).
Handle unlimited nesting depth for nested serializers of non-relational fields.
Initial beta release.