mirror of
https://github.com/encode/django-rest-framework.git
synced 2024-11-10 19:56:59 +03:00
Move library docs into seperate folder
This commit is contained in:
tom christie tom@tomchristie.com
parent
250ab0f609
commit
f6e534321a
|
|
@ -1,27 +0,0 @@
|
|||
:mod:`authenticators`
|
||||
=====================
|
||||
|
||||
.. module:: authenticators
|
||||
|
||||
The authenticators module provides a standard set of authentication methods that can be plugged in to a :class:`.Resource`, as well as providing a template by which to write custom authentication methods.
|
||||
|
||||
The base class
|
||||
--------------
|
||||
|
||||
All authenticators must subclass the :class:`BaseAuthenticator` class and override it's :func:`authenticate` method.
|
||||
|
||||
.. class:: BaseAuthenticator
|
||||
|
||||
.. method:: authenticate(request)
|
||||
|
||||
Authenticate the request and return the authentication context or None.
|
||||
|
||||
The default permission checking on :class:`.Resource` will use the allowed_methods attribute for permissions if the authentication context is not None, and use anon_allowed_methods otherwise.
|
||||
|
||||
The authentication context is passed to the handler calls (eg :meth:`.Resource.get`, :meth:`.Resource.post` etc...) in order to allow them to apply any more fine grained permission checking at the point the response is being generated.
|
||||
|
||||
This function must be overridden to be implemented.
|
||||
|
||||
Provided authenticators
|
||||
-----------------------
|
||||
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
:mod:`emitters`
|
||||
===============
|
||||
|
||||
The emitters module provides a set of emitters that can be plugged in to a :class:`.Resource`. An emitter is responsible for taking the output of a and serializing it to a given media type. A :class:`.Resource` can have a number of emitters, allow the same content to be serialized in a number of different formats depending on the requesting client's preferences, as specified in the HTTP Request's Accept header.
|
||||
|
||||
.. automodule:: emitters
|
||||
:members:
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
ModelResource
|
||||
=============
|
||||
|
||||
.. automodule:: modelresource
|
||||
:members:
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Parsers
|
||||
=======
|
||||
|
||||
.. automodule:: parsers
|
||||
:members:
|
||||
|
|
@ -1,136 +0,0 @@
|
|||
:mod:`resource`
|
||||
===============
|
||||
|
||||
.. module:: resource
|
||||
|
||||
The :mod:`resource` module is the core of FlyWheel. It provides the :class:`Resource` base class which handles incoming HTTP requests and maps them to method calls, performing authentication, input deserialization, input validation and output serialization.
|
||||
|
||||
Resources are created by sublassing :class:`Resource`, setting a number of class attributes, and overriding one or more methods.
|
||||
|
||||
.. class:: Resource
|
||||
|
||||
:class:`Resource` class attributes
|
||||
----------------------------------
|
||||
|
||||
The following class attributes determine the behavior of the Resource and are intended to be overridden.
|
||||
|
||||
.. attribute:: Resource.allowed_methods
|
||||
|
||||
A list of the HTTP methods that the Resource supports.
|
||||
HTTP requests to the resource that do not map to an allowed operation will result in a 405 Method Not Allowed response.
|
||||
|
||||
Default: ``('GET',)``
|
||||
|
||||
.. attribute:: Resource.anon_allowed_methods
|
||||
|
||||
A list of the HTTP methods that the Resource supports for unauthenticated users.
|
||||
Unauthenticated HTTP requests to the resource that do not map to an allowed operation will result in a 405 Method Not Allowed response.
|
||||
|
||||
Default: ``()``
|
||||
|
||||
.. attribute:: Resource.emitters
|
||||
|
||||
The list of emitters that the Resource supports. This determines which media types the resource can serialize it's output to. Clients can specify which media types they accept using standard HTTP content negotiation via the Accept header. (See `RFC 2616 - Sec 14.1 <http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html>`_) Clients can also override this standard content negotiation by specifying a `_format` ...
|
||||
|
||||
The :mod:`emitters` module provides the :class:`BaseEmitter` class and a set of default emitters, including emitters for JSON and XML, as well as emitters for HTML and Plain Text which provide for a self documenting API.
|
||||
|
||||
The ordering of the Emitters is important as it determines an order of preference.
|
||||
|
||||
Default: ``(emitters.JSONEmitter, emitters.DocumentingHTMLEmitter, emitters.DocumentingXHTMLEmitter, emitters.DocumentingPlainTextEmitter, emitters.XMLEmitter)``
|
||||
|
||||
.. attribute:: Resource.parsers
|
||||
|
||||
The list of parsers that the Resource supports. This determines which media types the resource can accept as input for incoming HTTP requests. (Typically PUT and POST requests).
|
||||
|
||||
The ordering of the Parsers may be considered informative of preference but is not used ...
|
||||
|
||||
Default: ``(parsers.JSONParser, parsers.XMLParser, parsers.FormParser)``
|
||||
|
||||
.. attribute:: Resource.authenticators
|
||||
|
||||
The list of authenticators that the Resource supports. This determines which authentication methods (eg Basic, Digest, OAuth) are used to authenticate requests.
|
||||
|
||||
Default: ``(authenticators.UserLoggedInAuthenticator, authenticators.BasicAuthenticator)``
|
||||
|
||||
.. attribute:: Resource.form
|
||||
|
||||
If not None, this attribute should be a Django form which will be used to validate any request data.
|
||||
This attribute is typically only used for POST or PUT requests to the resource.
|
||||
|
||||
Deafult: ``None``
|
||||
|
||||
.. attribute:: Resource.callmap
|
||||
|
||||
Maps HTTP methods to function calls on the :class:`Resource`. It may be overridden in order to add support for other HTTP methods such as HEAD, OPTIONS and PATCH, or in order to map methods to different function names, for example to use a more `CRUD <http://en.wikipedia.org/wiki/Create,_read,_update_and_delete>`_ like style.
|
||||
|
||||
Default: ``{ 'GET': 'get', 'POST': 'post', 'PUT': 'put', 'DELETE': 'delete' }``
|
||||
|
||||
|
||||
:class:`Resource` methods
|
||||
-------------------------
|
||||
|
||||
.. method:: Resource.get
|
||||
.. method:: Resource.post
|
||||
.. method:: Resource.put
|
||||
.. method:: Resource.delete
|
||||
.. method:: Resource.authenticate
|
||||
.. method:: Resource.reverse
|
||||
|
||||
:class:`Resource` properties
|
||||
----------------------------
|
||||
|
||||
.. method:: Resource.name
|
||||
.. method:: Resource.description
|
||||
.. method:: Resource.default_emitter
|
||||
.. method:: Resource.default_parser
|
||||
.. method:: Resource.emitted_media_types
|
||||
.. method:: Resource.parsed_media_types
|
||||
|
||||
:class:`Resource` reserved form and query parameters
|
||||
----------------------------------------------------
|
||||
|
||||
.. attribute:: Resource.ACCEPT_QUERY_PARAM
|
||||
|
||||
If set, allows the default `Accept:` header content negotiation to be bypassed by setting the requested media type in a query parameter on the URL. This can be useful if it is necessary to be able to hyperlink to a given format on the Resource using standard HTML.
|
||||
|
||||
Set to None to disable, or to another string value to use another name for the reserved URL query parameter.
|
||||
|
||||
Default: ``"_accept"``
|
||||
|
||||
.. attribute:: Resource.METHOD_PARAM
|
||||
|
||||
If set, allows for PUT and DELETE requests to be tunneled on form POST operations, by setting a (typically hidden) form field with the method name. This allows standard HTML forms to perform method requests which would otherwise `not be supported <http://dev.w3.org/html5/spec/Overview.html#attr-fs-method>`_
|
||||
|
||||
Set to None to disable, or to another string value to use another name for the reserved form field.
|
||||
|
||||
Default: ``"_method"``
|
||||
|
||||
.. attribute:: Resource.CONTENTTYPE_PARAM
|
||||
|
||||
Used together with :attr:`CONTENT_PARAM`.
|
||||
|
||||
If set, allows for arbitrary content types to be tunneled on form POST operations, by setting a form field with the content type. This allows standard HTML forms to perform requests with content types other those `supported by default <http://dev.w3.org/html5/spec/Overview.html#attr-fs-enctype>`_ (ie. `application/x-www-form-urlencoded`, `multipart/form-data`, and `text-plain`)
|
||||
|
||||
Set to None to disable, or to another string value to use another name for the reserved form field.
|
||||
|
||||
Default: ``"_contenttype"``
|
||||
|
||||
.. attribute:: Resource.CONTENT_PARAM
|
||||
|
||||
Used together with :attr:`CONTENTTYPE_PARAM`.
|
||||
|
||||
Set to None to disable, or to another string value to use another name for the reserved form field.
|
||||
|
||||
Default: ``"_content"``
|
||||
|
||||
.. attribute:: Resource.CSRF_PARAM
|
||||
|
||||
The name used in Django's (typically hidden) form field for `CSRF Protection <http://docs.djangoproject.com/en/dev/ref/contrib/csrf/>`_.
|
||||
|
||||
Setting to None does not disable Django's CSRF middleware, but it does mean that the field name will not be treated as reserved by FlyWheel, so for example the default :class:`FormParser` will return fields with this as part of the request content, rather than ignoring them.
|
||||
|
||||
Default:: ``"csrfmiddlewaretoken"``
|
||||
|
||||
reserved params
|
||||
internal methods
|
||||
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Response
|
||||
========
|
||||
|
||||
.. automodule:: response
|
||||
:members:
|
||||
Loading…
Reference in New Issue
Block a user