@@ -95,17 +95,53 @@ Here's an example of using the new decorators. Firstly we have a detail-type rou
...
@@ -95,17 +95,53 @@ Here's an example of using the new decorators. Firstly we have a detail-type rou
serializer = self.get_pagination_serializer(page)
serializer = self.get_pagination_serializer(page)
return Response(serializer.data)
return Response(serializer.data)
For more details, see the [viewsets](../api-guide/viewsets.md) documentation.
For more details, see the [viewsets documentation](../api-guide/viewsets.md).
## Other features
## Other features
## Deprecations
There are also a number of other features and bugfixes as [listed in the release notes][2-4-release-notes]. In particular these include:
[Customizable view name and description functions][view-name-and-description-settings] for use with the browsable API, by using the `VIEW_NAME_FUNCTION` and `VIEW_DESCRIPTION_FUNCTION` settings.
Smarter [client IP identification for throttling][client-ip-identification], with the addition of the `NUM_PROXIES` setting.
## Deprecations
All API changes in 2.3 that previously raised `PendingDeprecationWarning` will now raise a `DeprecationWarning`, which is loud by default.
All API changes in 2.3 that previously raised `DeprecationWarning` have now been removed entirely.
Furter details on these deprecations is available in the [2.3 announcement][2-3-announcement].
## Labels and milestones
## Labels and milestones
TODO
Although not strictly part of the 2.4 release it's also worth noting here that we've been working hard towards improving our triage process.
The [labels that we use in GitHub][github-labels] have been cleaned up, and all existing tickets triaged. Any given ticket should have one and only one label, indicating its current state.
We've also [started using milestones][github-milestones] in order to track tickets against particular releases.
---
**Above**: *Overview of our current use of labels and milestones in GitHub.*
---
We hope both of these changes will help make the management process more clear and obvious and help keep tickets well-organised and relevant.
## Next steps
The next planned release will be 3.0, featuring an improved and simplified serializer implementation.
*`allow_none` for char fields
Once again, many thanks to all the generous [backers and sponsors][kickstarter-sponsors] who've helped make this possible!
*`trailing_slash = True` --> `[^/]`, `trailing_slash = False` --> `[^/.]`, becomes simply `[^/]` and `lookup_value_regex` is added.
