From 362061b24ce3f5d187a4a3a14f566c1653bccfb9 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Tue, 2 Feb 2010 03:18:21 +0000 Subject: - Remove ``view_header``, ``view_accept``, ``view_xhr``, ``view_path_info``, ``view_request_method``, ``view_request_param``, and ``view_containment`` predicate arguments from the ``Configurator.add_route`` argument list. These arguments were speculative. If you need the features exposed by these arguments, add a view associated with a route using the ``route_name`` argument to the ``add_view`` method instead. - Remove ``view_header``, ``view_accept``, ``view_xhr``, ``view_path_info``, ``view_request_method``, ``view_request_param``, and ``view_containment`` predicate arguments from the ``route`` ZCML directive attribute set. These attributes were speculative. If you need the features exposed by these attributes, add a view associated with a route using the ``route_name`` attribute of the ``view`` ZCML directive instead. --- docs/narr/urldispatch.rst | 21 --------------------- docs/zcml/route.rst | 25 ------------------------- 2 files changed, 46 deletions(-) (limited to 'docs') diff --git a/docs/narr/urldispatch.rst b/docs/narr/urldispatch.rst index 495b05a14..d766eba09 100644 --- a/docs/narr/urldispatch.rst +++ b/docs/narr/urldispatch.rst @@ -550,27 +550,6 @@ information. This argument can also be spelled as ``renderer``. -``view_request_type`` - A reference to an :term:`interface` representing a :term:`request - type`. If this argument is not specified, any request type will be - considered a match for the view associated with this route. - - If the ``view`` argument is not provided, this argument has - no effect. - - This argument can also be spelled as ``request_type``. - -``view_containment`` - This value should be a reference to a Python class or - :term:`interface` that a parent object in the :term:`lineage` must - provide in order for the view related to this route to be found and - called. Your models must be 'location-aware' to use this feature. - See :ref:`location_aware` for more information about - location-awareness. - - If the ``view`` argument is not provided, this argument has no - effect. - ``view_attr`` The view machinery defaults to using the ``__call__`` method of the view callable (or the function itself, if the view callable is a diff --git a/docs/zcml/route.rst b/docs/zcml/route.rst index 169252d77..8bee3c14f 100644 --- a/docs/zcml/route.rst +++ b/docs/zcml/route.rst @@ -162,31 +162,6 @@ Attributes .. note:: This feature is new as of :mod:`repoze.bfg` 1.1. -``view_request_type`` - A :term:`dotted Python name` to an interface representing a - :term:`request type`. If this argument is not specified, any - request type will be considered a match for the view associated with - this route. - - If the ``view`` attribute is not provided, this attribute has no - effect. - - This attribute can also be spelled as ``request_type``. - -``view_containment`` - This value should be a :term:`dotted Python name` string - representing the class that a graph traversal parent object of the - :term:`context` must be an instance of (or :term:`interface` that a - parent object must provide) in order for this view to be found and - called. Your models must be "location-aware" to use this feature. - See :ref:`location_aware` for more information about - location-awareness. - - If the ``view`` attribute is not provided, this attribute has no - effect. - - .. note:: This feature is new as of :mod:`repoze.bfg` 1.1. - ``view_attr`` The view machinery defaults to using the ``__call__`` method of the view callable (or the function itself, if the view callable is a -- cgit v1.2.3