@@ -195,7 +195,7 @@ These override points are also particularly useful for adding behavior that occu
...
@@ -195,7 +195,7 @@ These override points are also particularly useful for adding behavior that occu
You won't typically need to override the following methods, although you might need to call into them if you're writing custom views using `GenericAPIView`.
You won't typically need to override the following methods, although you might need to call into them if you're writing custom views using `GenericAPIView`.
*`get_serializer_context(self)` - Returns a dictionary containing any extra context that should be supplied to the serializer. Defaults to including `'request'`, `'view'` and `'format'` keys.
*`get_serializer_context(self)` - Returns a dictionary containing any extra context that should be supplied to the serializer. Defaults to including `'request'`, `'view'` and `'format'` keys.
*`get_serializer(self, instance=None, data=None, many=False, partial=False)` - Returns a serializer instance.
*`get_paginated_response(self, data)` - Returns a paginated style `Response` object.
*`get_paginated_response(self, data)` - Returns a paginated style `Response` object.
*`paginate_queryset(self, queryset)` - Paginate a queryset if required, either returning a page object, or `None` if pagination is not configured for this view.
*`paginate_queryset(self, queryset)` - Paginate a queryset if required, either returning a page object, or `None` if pagination is not configured for this view.
*`filter_queryset(self, queryset)` - Given a queryset, filter it with whichever filter backends are in use, returning a new queryset.
*`filter_queryset(self, queryset)` - Given a queryset, filter it with whichever filter backends are in use, returning a new queryset.