mirror of
https://github.com/encode/django-rest-framework.git
synced 2024-11-24 02:24:03 +03:00
Rense VanderHoek
commit
8348008781
|
|
@ -21,10 +21,10 @@ env:
|
|||
- TOX_ENV=py26-django15
|
||||
- TOX_ENV=py27-django14
|
||||
- TOX_ENV=py26-django14
|
||||
- TOX_ENV=py34-django18alpha
|
||||
- TOX_ENV=py33-django18alpha
|
||||
- TOX_ENV=py32-django18alpha
|
||||
- TOX_ENV=py27-django18alpha
|
||||
- TOX_ENV=py34-django18beta
|
||||
- TOX_ENV=py33-django18beta
|
||||
- TOX_ENV=py32-django18beta
|
||||
- TOX_ENV=py27-django18beta
|
||||
|
||||
install:
|
||||
- pip install tox
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ There is a live example API for testing purposes, [available here][sandbox].
|
|||
# Requirements
|
||||
|
||||
* Python (2.6.5+, 2.7, 3.2, 3.3, 3.4)
|
||||
* Django (1.4.11+, 1.5.6+, 1.6.3+, 1.7, 1.8-alpha)
|
||||
* Django (1.4.11+, 1.5.6+, 1.6.3+, 1.7, 1.8-beta)
|
||||
|
||||
# Installation
|
||||
|
||||
|
|
|
|||
|
|
@ -353,6 +353,10 @@ HTTP Signature (currently a [IETF draft][http-signature-ietf-draft]) provides a
|
|||
|
||||
[Djoser][djoser] library provides a set of views to handle basic actions such as registration, login, logout, password reset and account activation. The package works with a custom user model and it uses token based authentication. This is a ready to use REST implementation of Django authentication system.
|
||||
|
||||
## django-rest-auth
|
||||
|
||||
[Django-rest-auth][django-rest-auth] library provides a set of REST API endpoints for registration, authentication (including social media authentication), password reset, retrieve and update user details, etc. By having these API endpoints, your client apps such as AngularJS, iOS, Android, and others can communicate to your Django backend site independently via REST APIs for user management.
|
||||
|
||||
[cite]: http://jacobian.org/writing/rest-worst-practices/
|
||||
[http401]: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.2
|
||||
[http403]: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.4
|
||||
|
|
@ -392,3 +396,4 @@ HTTP Signature (currently a [IETF draft][http-signature-ietf-draft]) provides a
|
|||
[mohawk]: http://mohawk.readthedocs.org/en/latest/
|
||||
[mac]: http://tools.ietf.org/html/draft-hammer-oauth-v2-mac-token-05
|
||||
[djoser]: https://github.com/sunscrapers/djoser
|
||||
[django-rest-auth]: https://github.com/Tivix/django-rest-auth
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ Any example validation error might look like this:
|
|||
|
||||
You can implement custom exception handling by creating a handler function that converts exceptions raised in your API views into response objects. This allows you to control the style of error responses used by your API.
|
||||
|
||||
The function must take a single argument, which is the exception to be handled, and should either return a `Response` object, or return `None` if the exception cannot be handled. If the handler returns `None` then the exception will be re-raised and Django will return a standard HTTP 500 'server error' response.
|
||||
The function must take a pair of arguments, this first is the exception to be handled, and the second is a dictionary containing any extra context such as the view currently being handled. The exception handler function should either return a `Response` object, or return `None` if the exception cannot be handled. If the handler returns `None` then the exception will be re-raised and Django will return a standard HTTP 500 'server error' response.
|
||||
|
||||
For example, you might want to ensure that all error responses include the HTTP status code in the body of the response, like so:
|
||||
|
||||
|
|
@ -72,6 +72,8 @@ In order to alter the style of the response, you could write the following custo
|
|||
|
||||
return response
|
||||
|
||||
The context argument is not used by the default handler, but can be useful if the exception handler needs further information such as the view currently being handled, which can be accessed as `context['view']`.
|
||||
|
||||
The exception handler must also be configured in your settings, using the `EXCEPTION_HANDLER` setting key. For example:
|
||||
|
||||
REST_FRAMEWORK = {
|
||||
|
|
|
|||
|
|
@ -32,14 +32,14 @@ You can also set the pagination class on an individual view by using the `pagina
|
|||
If you want to modify particular aspects of the pagination style, you'll want to override one of the pagination classes, and set the attributes that you want to change.
|
||||
|
||||
class LargeResultsSetPagination(PageNumberPagination):
|
||||
paginate_by = 1000
|
||||
paginate_by_param = 'page_size'
|
||||
max_paginate_by = 10000
|
||||
page_size = 1000
|
||||
page_size_query_param = 'page_size'
|
||||
max_page_size = 10000
|
||||
|
||||
class StandardResultsSetPagination(PageNumberPagination):
|
||||
paginate_by = 100
|
||||
paginate_by_param = 'page_size'
|
||||
max_paginate_by = 1000
|
||||
page_size = 100
|
||||
page_size_query_param = 'page_size'
|
||||
max_page_size = 1000
|
||||
|
||||
You can then apply your new style to a view using the `.pagination_class` attribute:
|
||||
|
||||
|
|
@ -59,15 +59,141 @@ Or apply the style globally, using the `DEFAULT_PAGINATION_CLASS` settings key.
|
|||
|
||||
## PageNumberPagination
|
||||
|
||||
**TODO**
|
||||
This pagination style accepts a single number page number in the request query parameters.
|
||||
|
||||
**Request**:
|
||||
|
||||
GET https://api.example.org/accounts/?page=4
|
||||
|
||||
**Response**:
|
||||
|
||||
HTTP 200 OK
|
||||
{
|
||||
"count": 1023
|
||||
"next": "https://api.example.org/accounts/?page=5",
|
||||
"previous": "https://api.example.org/accounts/?page=3",
|
||||
"results": [
|
||||
…
|
||||
]
|
||||
}
|
||||
|
||||
#### Setup
|
||||
|
||||
To enable the `PageNumberPagination` style globally, use the following configuration, modifying the `DEFAULT_PAGE_SIZE` as desired:
|
||||
|
||||
REST_FRAMEWORK = {
|
||||
'DEFAULT_PAGINATION_CLASS': 'rest_framework.pagination.PageNumberPagination',
|
||||
'DEFAULT_PAGE_SIZE': 100
|
||||
}
|
||||
|
||||
On `GenericAPIView` subclasses you may also set the `pagination_class` attribute to select `PageNumberPagination` on a per-view basis.
|
||||
|
||||
#### Configuration
|
||||
|
||||
The `PageNumberPagination` class includes a number of attributes that may be overridden to modify the pagination style.
|
||||
|
||||
To set these attributes you should override the `PageNumberPagination` class, and then enable your custom pagination class as above.
|
||||
|
||||
* `page_size` - A numeric value indicating the page size. If set, this overrides the `DEFAULT_PAGE_SIZE` setting. Defaults to the same value as the `DEFAULT_PAGE_SIZE` settings key.
|
||||
* `page_query_param` - A string value indicating the name of the query parameter to use for the pagination control.
|
||||
* `page_size_query_param` - If set, this is a string value indicating the name of a query parameter that allows the client to set the page size on a per-request basis. Defaults to `None`, indicating that the client may not control the requested page size.
|
||||
* `max_page_size` - If set, this is a numeric value indicating the maximum allowable requested page size. This attribute is only valid if `page_size_query_param` is also set.
|
||||
* `last_page_strings` - A list or tuple of string values indicating values that may be used with the `page_query_param` to request the final page in the set. Defaults to `('last',)`
|
||||
* `template` - The name of a template to use when rendering pagination controls in the browsable API. May be overridden to modify the rendering style, or set to `None` to disable HTML pagination controls completely. Defaults to `"rest_framework/pagination/numbers.html"`.
|
||||
|
||||
---
|
||||
|
||||
## LimitOffsetPagination
|
||||
|
||||
**TODO**
|
||||
This pagination style mirrors the syntax used when looking up multiple database records. The client includes both a "limit" and an
|
||||
"offset" query parameter. The limit indicates the maximum number of items to return, and is equivalent to the `page_size` in other styles. The offset indicates the starting position of the query in relation to the complete set of unpaginated items.
|
||||
|
||||
**Request**:
|
||||
|
||||
GET https://api.example.org/accounts/?limit=100&offset=400
|
||||
|
||||
**Response**:
|
||||
|
||||
HTTP 200 OK
|
||||
{
|
||||
"count": 1023
|
||||
"next": "https://api.example.org/accounts/?limit=100&offset=500",
|
||||
"previous": "https://api.example.org/accounts/?limit=100&offset=300",
|
||||
"results": [
|
||||
…
|
||||
]
|
||||
}
|
||||
|
||||
#### Setup
|
||||
|
||||
To enable the `PageNumberPagination` style globally, use the following configuration:
|
||||
|
||||
REST_FRAMEWORK = {
|
||||
'DEFAULT_PAGINATION_CLASS': 'rest_framework.pagination.LimitOffsetPagination'
|
||||
}
|
||||
|
||||
Optionally, you may also set a `DEFAULT_PAGE_SIZE` key. If the `DEFAULT_PAGE_SIZE` parameter is also used then the `limit` query parameter will be optional, and may be omitted by the client.
|
||||
|
||||
On `GenericAPIView` subclasses you may also set the `pagination_class` attribute to select `LimitOffsetPagination` on a per-view basis.
|
||||
|
||||
#### Configuration
|
||||
|
||||
The `LimitOffsetPagination` class includes a number of attributes that may be overridden to modify the pagination style.
|
||||
|
||||
To set these attributes you should override the `LimitOffsetPagination` class, and then enable your custom pagination class as above.
|
||||
|
||||
* `default_limit` - A numeric value indicating the limit to use if one is not provided by the client in a query parameter. Defaults to the same value as the `DEFAULT_PAGE_SIZE` settings key.
|
||||
* `limit_query_param` - A string value indicating the name of the "limit" query parameter. Defaults to `'limit'`.
|
||||
* `offset_query_param` - A string value indicating the name of the "offset" query parameter. Defaults to `'offset'`.
|
||||
* `max_limit` - If set this is a numeric value indicating the maximum allowable limit that may be requested by the client. Defaults to `None`.
|
||||
* `template` - The name of a template to use when rendering pagination controls in the browsable API. May be overridden to modify the rendering style, or set to `None` to disable HTML pagination controls completely. Defaults to `"rest_framework/pagination/numbers.html"`.
|
||||
|
||||
---
|
||||
|
||||
## CursorPagination
|
||||
|
||||
**TODO**
|
||||
The cursor-based pagination presents an opaque "cursor" indicator that the client may use to page through the result set. This pagination style only presents forward and reverse controls, and does not allow the client to navigate to arbitrary positions.
|
||||
|
||||
Cursor based pagination requires that there is a unique, unchanging ordering of items in the result set. This ordering might typically be a creation timestamp on the records, as this presents a consistent ordering to paginate against.
|
||||
|
||||
Cursor based pagination is more complex than other schemes. It also requires that the result set presents a fixed ordering, and does not allow the client to arbitrarily index into the result set. However it does provide the following benefits:
|
||||
|
||||
* Provides a consistent pagination view. When used properly `CursorPagination` ensures that the client will never see the same item twice when paging through records.
|
||||
* Supports usage with very large datasets. With extremely large datasets pagination using offset-based pagination styles may become inefficient or unusable. Cursor based pagination schemes instead have fixed-time properties, and do not slow down as the dataset size increases.
|
||||
|
||||
#### Details and limitations
|
||||
|
||||
This implementation of cursor pagination uses a smart "position plus offset" style that allows it to properly support not-strictly-unique values as the ordering.
|
||||
|
||||
It should be noted that using non-unique values the ordering does introduce the possibility of paging artifacts, where pagination consistency is no longer 100% guaranteed.
|
||||
|
||||
**TODO**: Notes on `None`.
|
||||
|
||||
The implementation also supports both forward and reverse pagination, which is often not supported in other implementations.
|
||||
|
||||
For more technical details on the implementation we use for cursor pagination, the ["Building cursors for the Disqus API"][disqus-cursor-api] blog post gives a good overview of the basic approach.
|
||||
|
||||
#### Setup
|
||||
|
||||
To enable the `CursorPagination` style globally, use the following configuration, modifying the `DEFAULT_PAGE_SIZE` as desired:
|
||||
|
||||
REST_FRAMEWORK = {
|
||||
'DEFAULT_PAGINATION_CLASS': 'rest_framework.pagination.CursorPagination',
|
||||
'DEFAULT_PAGE_SIZE': 100
|
||||
}
|
||||
|
||||
On `GenericAPIView` subclasses you may also set the `pagination_class` attribute to select `CursorPagination` on a per-view basis.
|
||||
|
||||
#### Configuration
|
||||
|
||||
The `CursorPagination` class includes a number of attributes that may be overridden to modify the pagination style.
|
||||
|
||||
To set these attributes you should override the `CursorPagination` class, and then enable your custom pagination class as above.
|
||||
|
||||
* `page_size` = A numeric value indicating the page size. If set, this overrides the `DEFAULT_PAGE_SIZE` setting. Defaults to the same value as the `DEFAULT_PAGE_SIZE` settings key.
|
||||
* `cursor_query_param` = A string value indicating the name of the "cursor" query parameter. Defaults to `'cursor'`.
|
||||
* `ordering` = This should be a string, or list of strings, indicating the field against which the cursor based pagination will be applied. For example: `ordering = 'created'`. Any filters on the view which define a `get_ordering` will override this attribute. Defaults to `None`.
|
||||
* `template` = The name of a template to use when rendering pagination controls in the browsable API. May be overridden to modify the rendering style, or set to `None` to disable HTML pagination controls completely. Defaults to `"rest_framework/pagination/previous_and_next.html"`.
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -108,7 +234,7 @@ To have your custom pagination class be used by default, use the `DEFAULT_PAGINA
|
|||
|
||||
REST_FRAMEWORK = {
|
||||
'DEFAULT_PAGINATION_CLASS': 'my_project.apps.core.pagination.LinkHeaderPagination',
|
||||
'PAGINATE_BY': 10
|
||||
'DEFAULT_PAGE_SIZE': 10
|
||||
}
|
||||
|
||||
API responses for list endpoints will now include a `Link` header, instead of including the pagination links as part of the body of the response, for example:
|
||||
|
|
@ -123,8 +249,25 @@ API responses for list endpoints will now include a `Link` header, instead of in
|
|||
|
||||
# HTML pagination controls
|
||||
|
||||
By default using the pagination classes will cause HTML pagination controls to be displayed in the browsable API. There are two built-in display styles. The `PageNumberPagination` and `LimitOffsetPagination` classes display a list of page numbers with previous and next controls. The `CursorPagination` class displays a simpler style that only displays a previous and next control.
|
||||
|
||||
## Customizing the controls
|
||||
|
||||
You can override the templates that render the HTML pagination controls. The two built-in styles are:
|
||||
|
||||
* `rest_framework/pagination/numbers.html`
|
||||
* `rest_framework/pagination/previous_and_next.html`
|
||||
|
||||
Providing a template with either of these paths in a global template directory will override the default rendering for the relevant pagination classes.
|
||||
|
||||
Alternatively you can disable HTML pagination controls completely by subclassing on of the existing classes, setting `template = None` as an attribute on the class. You'll then need to configure your `DEFAULT_PAGINATION_CLASS` settings key to use your custom class as the default pagination style.
|
||||
|
||||
#### Low-level API
|
||||
|
||||
The low-level API for determining if a pagination class should display the controls or not is exposed as a `display_page_controls` attribute on the pagination instance. Custom pagination classes should be set to `True` in the `paginate_queryset` method if they require the HTML pagination controls to be displayed.
|
||||
|
||||
The `.to_html()` and `.get_html_context()` methods may also be overridden in a custom pagination class in order to further customize how the controls are rendered.
|
||||
|
||||
---
|
||||
|
||||
# Third party packages
|
||||
|
|
@ -140,3 +283,4 @@ The [`DRF-extensions` package][drf-extensions] includes a [`PaginateByMaxMixin`
|
|||
[link-header]: ../img/link-header-pagination.png
|
||||
[drf-extensions]: http://chibisov.github.io/drf-extensions/docs/
|
||||
[paginate-by-max-mixin]: http://chibisov.github.io/drf-extensions/docs/#paginatebymaxmixin
|
||||
[disqus-cursor-api]: http://cramer.io/2011/03/08/building-cursors-for-the-disqus-api/
|
||||
|
|
@ -14,7 +14,7 @@ Extends [Django's existing `RequestFactory` class][requestfactory].
|
|||
|
||||
## Creating test requests
|
||||
|
||||
The `APIRequestFactory` class supports an almost identical API to Django's standard `RequestFactory` class. This means the that standard `.get()`, `.post()`, `.put()`, `.patch()`, `.delete()`, `.head()` and `.options()` methods are all available.
|
||||
The `APIRequestFactory` class supports an almost identical API to Django's standard `RequestFactory` class. This means that the standard `.get()`, `.post()`, `.put()`, `.patch()`, `.delete()`, `.head()` and `.options()` methods are all available.
|
||||
|
||||
from rest_framework.test import APIRequestFactory
|
||||
|
||||
|
|
@ -115,7 +115,7 @@ Extends [Django's existing `Client` class][client].
|
|||
|
||||
## Making requests
|
||||
|
||||
The `APIClient` class supports the same request interface as `APIRequestFactory`. This means the that standard `.get()`, `.post()`, `.put()`, `.patch()`, `.delete()`, `.head()` and `.options()` methods are all available. For example:
|
||||
The `APIClient` class supports the same request interface as Django's standard `Client` class. This means the that standard `.get()`, `.post()`, `.put()`, `.patch()`, `.delete()`, `.head()` and `.options()` methods are all available. For example:
|
||||
|
||||
from rest_framework.test import APIClient
|
||||
|
||||
|
|
@ -269,6 +269,6 @@ For example, to add support for using `format='html'` in test requests, you migh
|
|||
}
|
||||
|
||||
[cite]: http://jacobian.org/writing/django-apps-with-buildout/#s-create-a-test-wrapper
|
||||
[client]: https://docs.djangoproject.com/en/dev/topics/testing/overview/#module-django.test.client
|
||||
[client]: https://docs.djangoproject.com/en/dev/topics/testing/tools/#the-test-client
|
||||
[requestfactory]: https://docs.djangoproject.com/en/dev/topics/testing/advanced/#django.test.client.RequestFactory
|
||||
[configuration]: #configuration
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@ Some reasons you might want to use REST framework:
|
|||
REST framework requires the following:
|
||||
|
||||
* Python (2.6.5+, 2.7, 3.2, 3.3, 3.4)
|
||||
* Django (1.4.11+, 1.5.6+, 1.6.3+, 1.7)
|
||||
* Django (1.4.11+, 1.5.6+, 1.6.3+, 1.7, 1.8-beta)
|
||||
|
||||
The following packages are optional:
|
||||
|
||||
|
|
|
|||
|
|
@ -188,6 +188,7 @@ To submit new content, [open an issue][drf-create-issue] or [create a pull reque
|
|||
* [hawkrest][hawkrest] - Provides Hawk HTTP Authorization.
|
||||
* [djangorestframework-httpsignature][djangorestframework-httpsignature] - Provides an easy to use HTTP Signature Authentication mechanism.
|
||||
* [djoser][djoser] - Provides a set of views to handle basic actions such as registration, login, logout, password reset and account activation.
|
||||
* [django-rest-auth][django-rest-auth] - Provides a set of REST API endpoints for registration, authentication (including social media authentication), password reset, retrieve and update user details, etc.
|
||||
|
||||
### Permissions
|
||||
|
||||
|
|
@ -324,3 +325,4 @@ To submit new content, [open an issue][drf-create-issue] or [create a pull reque
|
|||
[django-rest-framework-and-angularjs-video]: http://www.youtube.com/watch?v=q8frbgtj020
|
||||
[web-api-performance-profiling-django-rest-framework]: http://dabapps.com/blog/api-performance-profiling-django-rest-framework/
|
||||
[api-development-with-django-and-django-rest-framework]: https://bnotions.com/api-development-with-django-and-django-rest-framework/
|
||||
[django-rest-auth]: https://github.com/Tivix/django-rest-auth/
|
||||
|
|
|
|||
|
|
@ -71,7 +71,14 @@ def get_attribute(instance, attrs):
|
|||
except ObjectDoesNotExist:
|
||||
return None
|
||||
if is_simple_callable(instance):
|
||||
instance = instance()
|
||||
try:
|
||||
instance = instance()
|
||||
except (AttributeError, KeyError) as exc:
|
||||
# If we raised an Attribute or KeyError here it'd get treated
|
||||
# as an omitted field in `Field.get_attribute()`. Instead we
|
||||
# raise a ValueError to ensure the exception is not masked.
|
||||
raise ValueError('Exception raised in callable attribute "{0}"; original exception was: {1}'.format(attr, exc))
|
||||
|
||||
return instance
|
||||
|
||||
|
||||
|
|
@ -107,6 +114,8 @@ class CreateOnlyDefault:
|
|||
|
||||
def set_context(self, serializer_field):
|
||||
self.is_update = serializer_field.parent.instance is not None
|
||||
if callable(self.default) and hasattr(self.default, 'set_context'):
|
||||
self.default.set_context(serializer_field)
|
||||
|
||||
def __call__(self):
|
||||
if self.is_update:
|
||||
|
|
@ -1184,7 +1193,7 @@ class ListField(Field):
|
|||
|
||||
class DictField(Field):
|
||||
child = _UnvalidatedField()
|
||||
initial = []
|
||||
initial = {}
|
||||
default_error_messages = {
|
||||
'not_a_dict': _('Expected a dictionary of items but got type "{input_type}".')
|
||||
}
|
||||
|
|
|
|||
|
|
@ -259,7 +259,7 @@ class PageNumberPagination(BasePagination):
|
|||
)
|
||||
raise NotFound(msg)
|
||||
|
||||
if paginator.count > 1:
|
||||
if paginator.count > 1 and self.template is not None:
|
||||
# The browsable API should display pagination controls.
|
||||
self.display_page_controls = True
|
||||
|
||||
|
|
@ -347,7 +347,7 @@ class LimitOffsetPagination(BasePagination):
|
|||
self.offset = self.get_offset(request)
|
||||
self.count = _get_count(queryset)
|
||||
self.request = request
|
||||
if self.count > self.limit:
|
||||
if self.count > self.limit and self.template is not None:
|
||||
self.display_page_controls = True
|
||||
return queryset[self.offset:self.offset + self.limit]
|
||||
|
||||
|
|
@ -518,7 +518,7 @@ class CursorPagination(BasePagination):
|
|||
|
||||
# Display page controls in the browsable API if there is more
|
||||
# than one page.
|
||||
if self.has_previous or self.has_next:
|
||||
if (self.has_previous or self.has_next) and self.template is not None:
|
||||
self.display_page_controls = True
|
||||
|
||||
return self.page
|
||||
|
|
|
|||
|
|
@ -165,34 +165,30 @@ class SimpleRouter(BaseRouter):
|
|||
else:
|
||||
list_routes.append((httpmethods, methodname))
|
||||
|
||||
def _get_dynamic_routes(route, dynamic_routes):
|
||||
ret = []
|
||||
for httpmethods, methodname in dynamic_routes:
|
||||
method_kwargs = getattr(viewset, methodname).kwargs
|
||||
initkwargs = route.initkwargs.copy()
|
||||
initkwargs.update(method_kwargs)
|
||||
url_path = initkwargs.pop("url_path", None) or methodname
|
||||
ret.append(Route(
|
||||
url=replace_methodname(route.url, url_path),
|
||||
mapping=dict((httpmethod, methodname) for httpmethod in httpmethods),
|
||||
name=replace_methodname(route.name, url_path),
|
||||
initkwargs=initkwargs,
|
||||
))
|
||||
|
||||
return ret
|
||||
|
||||
ret = []
|
||||
for route in self.routes:
|
||||
if isinstance(route, DynamicDetailRoute):
|
||||
# Dynamic detail routes (@detail_route decorator)
|
||||
for httpmethods, methodname in detail_routes:
|
||||
method_kwargs = getattr(viewset, methodname).kwargs
|
||||
url_path = method_kwargs.pop("url_path", None) or methodname
|
||||
initkwargs = route.initkwargs.copy()
|
||||
initkwargs.update(method_kwargs)
|
||||
ret.append(Route(
|
||||
url=replace_methodname(route.url, url_path),
|
||||
mapping=dict((httpmethod, methodname) for httpmethod in httpmethods),
|
||||
name=replace_methodname(route.name, url_path),
|
||||
initkwargs=initkwargs,
|
||||
))
|
||||
ret += _get_dynamic_routes(route, detail_routes)
|
||||
elif isinstance(route, DynamicListRoute):
|
||||
# Dynamic list routes (@list_route decorator)
|
||||
for httpmethods, methodname in list_routes:
|
||||
method_kwargs = getattr(viewset, methodname).kwargs
|
||||
url_path = method_kwargs.pop("url_path", None) or methodname
|
||||
initkwargs = route.initkwargs.copy()
|
||||
initkwargs.update(method_kwargs)
|
||||
ret.append(Route(
|
||||
url=replace_methodname(route.url, url_path),
|
||||
mapping=dict((httpmethod, methodname) for httpmethod in httpmethods),
|
||||
name=replace_methodname(route.name, url_path),
|
||||
initkwargs=initkwargs,
|
||||
))
|
||||
ret += _get_dynamic_routes(route, list_routes)
|
||||
else:
|
||||
# Standard route
|
||||
ret.append(route)
|
||||
|
|
|
|||
|
|
@ -13,6 +13,7 @@ response content is handled by parsers and renderers.
|
|||
from __future__ import unicode_literals
|
||||
from django.db import models
|
||||
from django.db.models.fields import FieldDoesNotExist, Field as DjangoModelField
|
||||
from django.db.models import query
|
||||
from django.utils.translation import ugettext_lazy as _
|
||||
from rest_framework.compat import postgres_fields, unicode_to_repr
|
||||
from rest_framework.utils import model_meta
|
||||
|
|
@ -562,7 +563,7 @@ class ListSerializer(BaseSerializer):
|
|||
"""
|
||||
# Dealing with nested relationships, data can be a Manager,
|
||||
# so, first get a queryset from the Manager if needed
|
||||
iterable = data.all() if isinstance(data, models.Manager) else data
|
||||
iterable = data.all() if isinstance(data, (models.Manager, query.QuerySet)) else data
|
||||
return [
|
||||
self.child.to_representation(item) for item in iterable
|
||||
]
|
||||
|
|
|
|||
|
|
@ -1,11 +1,16 @@
|
|||
{% load i18n %}
|
||||
{% trans "No items to select." as no_items %}
|
||||
|
||||
<div class="form-group">
|
||||
{% if field.label %}
|
||||
<label class="col-sm-2 control-label {% if style.hide_label %}sr-only{% endif %}">{{ field.label }}</label>
|
||||
{% endif %}
|
||||
<div class="col-sm-10">
|
||||
<select multiple class="form-control" name="{{ field.name }}">
|
||||
<select multiple {{ field.choices|yesno:",disabled" }} class="form-control" name="{{ field.name }}">
|
||||
{% for key, text in field.choices.items %}
|
||||
<option value="{{ key }}" {% if key in field.value %}selected{% endif %}>{{ text }}</option>
|
||||
<option value="{{ key }}" {% if key in field.value %}selected{% endif %}>{{ text }}</option>
|
||||
{% empty %}
|
||||
<option>{{ no_items }}</option>
|
||||
{% endfor %}
|
||||
</select>
|
||||
{% if field.errors %}
|
||||
|
|
|
|||
|
|
@ -1,10 +1,15 @@
|
|||
{% load i18n %}
|
||||
{% trans "No items to select." as no_items %}
|
||||
|
||||
<div class="form-group {% if field.errors %}has-error{% endif %}">
|
||||
{% if field.label %}
|
||||
<label class="sr-only">{{ field.label }}</label>
|
||||
{% endif %}
|
||||
<select multiple class="form-control" name="{{ field.name }}">
|
||||
<select multiple {{ field.choices|yesno:",disabled" }} class="form-control" name="{{ field.name }}">
|
||||
{% for key, text in field.choices.items %}
|
||||
<option value="{{ key }}" {% if key in field.value %}selected{% endif %}>{{ text }}</option>
|
||||
<option value="{{ key }}" {% if key in field.value %}selected{% endif %}>{{ text }}</option>
|
||||
{% empty %}
|
||||
<option>{{ no_items }}</option>
|
||||
{% endfor %}
|
||||
</select>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -1,10 +1,15 @@
|
|||
{% load i18n %}
|
||||
{% trans "No items to select." as no_items %}
|
||||
|
||||
<div class="form-group {% if field.errors %}has-error{% endif %}">
|
||||
{% if field.label %}
|
||||
<label {% if style.hide_label %}class="sr-only"{% endif %}>{{ field.label }}</label>
|
||||
{% endif %}
|
||||
<select multiple class="form-control" name="{{ field.name }}">
|
||||
<select multiple {{ field.choices|yesno:",disabled" }} class="form-control" name="{{ field.name }}">
|
||||
{% for key, text in field.choices.items %}
|
||||
<option value="{{ key }}" {% if key in field.value %}selected{% endif %}>{{ text }}</option>
|
||||
<option value="{{ key }}" {% if key in field.value %}selected{% endif %}>{{ text }}</option>
|
||||
{% empty %}
|
||||
<option>{{ no_items }}</option>
|
||||
{% endfor %}
|
||||
</select>
|
||||
{% if field.errors %}
|
||||
|
|
|
|||
|
|
@ -209,7 +209,8 @@ class APIClient(APIRequestFactory, DjangoClient):
|
|||
self.handler._force_user = None
|
||||
self.handler._force_token = None
|
||||
|
||||
return super(APIClient, self).logout()
|
||||
if self.session:
|
||||
super(APIClient, self).logout()
|
||||
|
||||
|
||||
class APITransactionTestCase(testcases.TransactionTestCase):
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ from rest_framework.exceptions import ValidationError
|
|||
from rest_framework.utils.representation import smart_repr
|
||||
|
||||
|
||||
class UniqueValidator:
|
||||
class UniqueValidator(object):
|
||||
"""
|
||||
Validator that corresponds to `unique=True` on a model field.
|
||||
|
||||
|
|
@ -67,7 +67,7 @@ class UniqueValidator:
|
|||
))
|
||||
|
||||
|
||||
class UniqueTogetherValidator:
|
||||
class UniqueTogetherValidator(object):
|
||||
"""
|
||||
Validator that corresponds to `unique_together = (...)` on a model class.
|
||||
|
||||
|
|
@ -138,7 +138,12 @@ class UniqueTogetherValidator:
|
|||
queryset = self.queryset
|
||||
queryset = self.filter_queryset(attrs, queryset)
|
||||
queryset = self.exclude_current_instance(attrs, queryset)
|
||||
if queryset.exists():
|
||||
|
||||
# Ignore validation if any field is None
|
||||
checked_values = [
|
||||
value for field, value in attrs.items() if field in self.fields
|
||||
]
|
||||
if None not in checked_values and queryset.exists():
|
||||
field_names = ', '.join(self.fields)
|
||||
raise ValidationError(self.message.format(field_names=field_names))
|
||||
|
||||
|
|
@ -150,7 +155,7 @@ class UniqueTogetherValidator:
|
|||
))
|
||||
|
||||
|
||||
class BaseUniqueForValidator:
|
||||
class BaseUniqueForValidator(object):
|
||||
message = None
|
||||
missing_message = _('This field is required.')
|
||||
|
||||
|
|
|
|||
|
|
@ -93,6 +93,31 @@ class TestSource:
|
|||
"same as the field name. Remove the `source` keyword argument."
|
||||
)
|
||||
|
||||
def test_callable_source(self):
|
||||
class ExampleSerializer(serializers.Serializer):
|
||||
example_field = serializers.CharField(source='example_callable')
|
||||
|
||||
class ExampleInstance(object):
|
||||
def example_callable(self):
|
||||
return 'example callable value'
|
||||
|
||||
serializer = ExampleSerializer(ExampleInstance())
|
||||
assert serializer.data['example_field'] == 'example callable value'
|
||||
|
||||
def test_callable_source_raises(self):
|
||||
class ExampleSerializer(serializers.Serializer):
|
||||
example_field = serializers.CharField(source='example_callable', read_only=True)
|
||||
|
||||
class ExampleInstance(object):
|
||||
def example_callable(self):
|
||||
raise AttributeError('method call failed')
|
||||
|
||||
with pytest.raises(ValueError) as exc_info:
|
||||
serializer = ExampleSerializer(ExampleInstance())
|
||||
serializer.data.items()
|
||||
|
||||
assert 'method call failed' in str(exc_info.value)
|
||||
|
||||
|
||||
class TestReadOnly:
|
||||
def setup(self):
|
||||
|
|
@ -292,6 +317,25 @@ class TestCreateOnlyDefault:
|
|||
'text': 'example',
|
||||
}
|
||||
|
||||
def test_create_only_default_callable_sets_context(self):
|
||||
"""
|
||||
CreateOnlyDefault instances with a callable default should set_context
|
||||
on the callable if possible
|
||||
"""
|
||||
class TestCallableDefault:
|
||||
def set_context(self, serializer_field):
|
||||
self.field = serializer_field
|
||||
|
||||
def __call__(self):
|
||||
return "success" if hasattr(self, 'field') else "failure"
|
||||
|
||||
class TestSerializer(serializers.Serializer):
|
||||
context_set = serializers.CharField(default=serializers.CreateOnlyDefault(TestCallableDefault()))
|
||||
|
||||
serializer = TestSerializer(data={})
|
||||
assert serializer.is_valid()
|
||||
assert serializer.validated_data['context_set'] == 'success'
|
||||
|
||||
|
||||
# Tests for field input and output values.
|
||||
# ----------------------------------------
|
||||
|
|
|
|||
|
|
@ -99,11 +99,5 @@ class TestFileUploadParser(TestCase):
|
|||
filename = parser.get_filename(self.stream, None, self.parser_context)
|
||||
self.assertEqual(filename, 'ÀĥƦ.txt')
|
||||
|
||||
self.__replace_content_disposition('inline; filename=fallback.txt; filename*=utf-8--ÀĥƦ.txt')
|
||||
filename = parser.get_filename(self.stream, None, self.parser_context)
|
||||
# Malformed. Either None or 'fallback.txt' will be acceptable.
|
||||
# See also https://code.djangoproject.com/ticket/24209
|
||||
self.assertIn(filename, ('fallback.txt', None))
|
||||
|
||||
def __replace_content_disposition(self, disposition):
|
||||
self.parser_context['request'].META['HTTP_CONTENT_DISPOSITION'] = disposition
|
||||
|
|
|
|||
|
|
@ -302,12 +302,16 @@ class DynamicListAndDetailViewSet(viewsets.ViewSet):
|
|||
return Response({'method': 'link2'})
|
||||
|
||||
|
||||
class SubDynamicListAndDetailViewSet(DynamicListAndDetailViewSet):
|
||||
pass
|
||||
|
||||
|
||||
class TestDynamicListAndDetailRouter(TestCase):
|
||||
def setUp(self):
|
||||
self.router = SimpleRouter()
|
||||
|
||||
def test_list_and_detail_route_decorators(self):
|
||||
routes = self.router.get_routes(DynamicListAndDetailViewSet)
|
||||
def _test_list_and_detail_route_decorators(self, viewset):
|
||||
routes = self.router.get_routes(viewset)
|
||||
decorator_routes = [r for r in routes if not (r.name.endswith('-list') or r.name.endswith('-detail'))]
|
||||
|
||||
MethodNamesMap = namedtuple('MethodNamesMap', 'method_name url_path')
|
||||
|
|
@ -336,3 +340,9 @@ class TestDynamicListAndDetailRouter(TestCase):
|
|||
else:
|
||||
method_map = 'get'
|
||||
self.assertEqual(route.mapping[method_map], method_name)
|
||||
|
||||
def test_list_and_detail_route_decorators(self):
|
||||
self._test_list_and_detail_route_decorators(DynamicListAndDetailViewSet)
|
||||
|
||||
def test_inherited_list_and_detail_route_decorators(self):
|
||||
self._test_list_and_detail_route_decorators(SubDynamicListAndDetailViewSet)
|
||||
|
|
|
|||
|
|
@ -83,11 +83,37 @@ class UniquenessTogetherModel(models.Model):
|
|||
unique_together = ('race_name', 'position')
|
||||
|
||||
|
||||
class NullUniquenessTogetherModel(models.Model):
|
||||
"""
|
||||
Used to ensure that null values are not included when checking
|
||||
unique_together constraints.
|
||||
|
||||
Ignoring items which have a null in any of the validated fields is the same
|
||||
behavior that database backends will use when they have the
|
||||
unique_together constraint added.
|
||||
|
||||
Example case: a null position could indicate a non-finisher in the race,
|
||||
there could be many non-finishers in a race, but all non-NULL
|
||||
values *should* be unique against the given `race_name`.
|
||||
"""
|
||||
date_of_birth = models.DateField(null=True) # Not part of the uniqueness constraint
|
||||
race_name = models.CharField(max_length=100)
|
||||
position = models.IntegerField(null=True)
|
||||
|
||||
class Meta:
|
||||
unique_together = ('race_name', 'position')
|
||||
|
||||
|
||||
class UniquenessTogetherSerializer(serializers.ModelSerializer):
|
||||
class Meta:
|
||||
model = UniquenessTogetherModel
|
||||
|
||||
|
||||
class NullUniquenessTogetherSerializer(serializers.ModelSerializer):
|
||||
class Meta:
|
||||
model = NullUniquenessTogetherModel
|
||||
|
||||
|
||||
class TestUniquenessTogetherValidation(TestCase):
|
||||
def setUp(self):
|
||||
self.instance = UniquenessTogetherModel.objects.create(
|
||||
|
|
@ -182,6 +208,34 @@ class TestUniquenessTogetherValidation(TestCase):
|
|||
""")
|
||||
assert repr(serializer) == expected
|
||||
|
||||
def test_ignore_validation_for_null_fields(self):
|
||||
# None values that are on fields which are part of the uniqueness
|
||||
# constraint cause the instance to ignore uniqueness validation.
|
||||
NullUniquenessTogetherModel.objects.create(
|
||||
date_of_birth=datetime.date(2000, 1, 1),
|
||||
race_name='Paris Marathon',
|
||||
position=None
|
||||
)
|
||||
data = {
|
||||
'date': datetime.date(2000, 1, 1),
|
||||
'race_name': 'Paris Marathon',
|
||||
'position': None
|
||||
}
|
||||
serializer = NullUniquenessTogetherSerializer(data=data)
|
||||
assert serializer.is_valid()
|
||||
|
||||
def test_do_not_ignore_validation_for_null_fields(self):
|
||||
# None values that are not on fields part of the uniqueness constraint
|
||||
# do not cause the instance to skip validation.
|
||||
NullUniquenessTogetherModel.objects.create(
|
||||
date_of_birth=datetime.date(2000, 1, 1),
|
||||
race_name='Paris Marathon',
|
||||
position=1
|
||||
)
|
||||
data = {'date': None, 'race_name': 'Paris Marathon', 'position': 1}
|
||||
serializer = NullUniquenessTogetherSerializer(data=data)
|
||||
assert not serializer.is_valid()
|
||||
|
||||
|
||||
# Tests for `UniqueForDateValidator`
|
||||
# ----------------------------------
|
||||
|
|
|
|||
4
tox.ini
4
tox.ini
|
|
@ -3,7 +3,7 @@ envlist =
|
|||
py27-{flake8,docs},
|
||||
{py26,py27}-django14,
|
||||
{py26,py27,py32,py33,py34}-django{15,16},
|
||||
{py27,py32,py33,py34}-django{17,18alpha}
|
||||
{py27,py32,py33,py34}-django{17,18beta}
|
||||
|
||||
[testenv]
|
||||
commands = ./runtests.py --fast
|
||||
|
|
@ -14,7 +14,7 @@ deps =
|
|||
django15: Django==1.5.6 # Should track minimum supported
|
||||
django16: Django==1.6.3 # Should track minimum supported
|
||||
django17: Django==1.7.2 # Should track maximum supported
|
||||
django18alpha: https://www.djangoproject.com/download/1.8a1/tarball/
|
||||
django18beta: https://www.djangoproject.com/download/1.8b1/tarball/
|
||||
-rrequirements/requirements-testing.txt
|
||||
-rrequirements/requirements-optionals.txt
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user