Browse files

add docs for third-party view predicates

  • Loading branch information...
mcdonc committed Aug 6, 2012
1 parent 859e947 commit 0196b2a06ef66d2e8b33a03cc84373ab84ba44be
Showing with 117 additions and 0 deletions.
  1. +15 −0 CHANGES.txt
  2. +2 −0 docs/api/config.rst
  3. +6 −0 docs/glossary.rst
  4. +94 −0 docs/narr/hooks.rst
@@ -20,6 +20,21 @@ Bug Fixes
+- Third-party custom view and route predicates can now be added for use by
+ view authors via ``pyramid.config.Configurator.add_view_predicate`` and
+ ``pyramid.config.Configurator.add_route_predicate``. So, for example,
+ doing this::
+ config.add_view_predicate('abc', my.package.ABCPredicate)
+ Might allow a view author to do this in an application that configured that
+ predicate::
+ @view_config(abc=1)
+ See "Adding A Third Party View or Route Predicate" in the Hooks chapter for
+ more information.
- Custom objects can be made easily JSON-serializable in Pyramid by defining
a ``__json__`` method on the object's class. This method should return
values natively serializable by ``json.dumps`` (such as ints, lists,
@@ -66,6 +66,8 @@
.. automethod:: add_response_adapter
.. automethod:: add_traverser
.. automethod:: add_tween
+ .. automethod:: add_route_predicate
+ .. automethod:: add_view_predicate
.. automethod:: set_request_factory
.. automethod:: set_root_factory
.. automethod:: set_session_factory
@@ -994,3 +994,9 @@ Glossary
Aka ``gunicorn``, a fast :term:`WSGI` server that runs on UNIX under
Python 2.5+ (although at the time of this writing does not support
Python 3). See for detailed information.
+ predicate factory
+ A callable which is used by a third party during the registration of a
+ route or view predicates to extend the view and route configuration
+ system. See :ref:`registering_thirdparty_predicates` for more
+ information.
@@ -1232,3 +1232,97 @@ Displaying Tween Ordering
The ``ptweens`` command-line utility can be used to report the current
implict and explicit tween chains used by an application. See
+.. _registering_thirdparty_predicates:
+Adding A Third Party View or Route Predicate
+View and route predicates used during view configuration allow you to narrow
+the set of circumstances under which a view or route will match. For
+example, the ``request_method`` view predicate can be used to ensure a view
+callable is only invoked when the request's method is ``POST``:
+.. code-block:: python
+ @view_config(request_method='POST')
+ def someview(request):
+ ...
+Likewise, a similar predicate can be used as a *route* predicate:
+.. code-block:: python
+ config.add_route('name', '/foo', request_method='POST')
+Many other built-in predicates exists (``request_param``, and others). You
+can add third-party predicates to the list of available predicates by using
+one of :meth:`pyramid.config.Configurator.add_view_predicate` or
+:meth:`pyramid.config.Configurator.add_route_predicate`. The former adds a
+view predicate, the latter a route predicate.
+When using one of those APIs, you pass a *name* and a *factory* to add a
+predicate during Pyramid's configuration stage. For example:
+.. code-block:: python
+ config.add_view_predicate('content_type', ContentTypePredicate)
+The above example adds a new predicate named ``content_type`` to the list of
+available predicates for views. This will allow the following view
+configuration statement to work:
+.. code-block:: python
+ :linenos:
+ @view_config(content_type='File')
+ def aview(request): ...
+The first argument to :meth:`pyramid.config.Configurator.add_view_predicate`,
+the name, is a string representing the name that is expected to be passed to
+``view_config`` (or its imperative analogue ``add_view``).
+The second argument is a predicate factory. A predicate factory is most
+often a class with a constructor (``__init__``), a ``text`` method, a
+``phash`` method and a ``__call__`` method. For example:
+.. code-block:: python
+ :linenos:
+ class ContentTypePredicate(object):
+ def __init__(self, val, config):
+ self.val
+ def text(self):
+ return 'content_type = %s' % (self.val,)
+ phash = text
+ def __call__(self, context, request):
+ return getattr(context, 'content_type', None) == self.val
+The constructor of a predicate factory takes two arguments: ``val`` and
+``config``. The ``val`` argument will be the argument passed to
+``view_config`` (or ``add_view``). In the example above, it will be the
+string ``File``. The second arg, ``config`` will be the Configurator
+instance at the time of configuration.
+The ``text`` method must return a string. It should be useful to describe
+the behavior of the predicate in error messages.
+The ``phash`` method must return a string or a sequence of strings. It's
+most often the same as ``text``, as long as ``text`` uniquely describes the
+predicate's name and the value passed to the constructor. If ``text`` is
+more general, or doesn't describe things that way, ``phash`` should return a
+string with the name and the value serialized. The result of ``phash`` is
+not seen in output anywhere, it just informs the uniqueness constraints for
+view configuration.
+The ``__call__`` method of a predicate factory must accept a resource
+(``context``) and a request, and must return ``True`` or ``False``. It is
+the "meat" of the predicate.
+You can use the same predicate factory as both a view predicate and as a
+route predicate, but you'll need to call ``add_view_predicate`` and
+``add_route_predicate`` separately with the same factory.

0 comments on commit 0196b2a

Please sign in to comment.