diff options
| author | Steve Piercy <web@stevepiercy.com> | 2015-10-12 03:20:14 -0700 |
|---|---|---|
| committer | Steve Piercy <web@stevepiercy.com> | 2015-10-12 03:20:14 -0700 |
| commit | 2637158227f6e53acb1dbc40953377b797ac8e23 (patch) | |
| tree | 8dc392dd738e1fe2a9c73fa2398cdb6be84ef1a2 | |
| parent | 8038177494a2bee1394fcb24357435662093fbe8 (diff) | |
| download | pyramid-2637158227f6e53acb1dbc40953377b797ac8e23.tar.gz pyramid-2637158227f6e53acb1dbc40953377b797ac8e23.tar.bz2 pyramid-2637158227f6e53acb1dbc40953377b797ac8e23.zip | |
rewrap 79 cols
| -rw-r--r-- | docs/narr/viewconfig.rst | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/docs/narr/viewconfig.rst b/docs/narr/viewconfig.rst index cb3e78be3..a7d0848ca 100644 --- a/docs/narr/viewconfig.rst +++ b/docs/narr/viewconfig.rst @@ -193,20 +193,20 @@ Non-Predicate Arguments the first element of ``None``, i.e., ``(None, {'public':True})``. ``wrapper`` - The :term:`view name` of a different :term:`view configuration` which will - receive the response body of this view as the ``request.wrapped_body`` - attribute of its own :term:`request`, and the :term:`response` returned by - this view as the ``request.wrapped_response`` attribute of its own request. - Using a wrapper makes it possible to "chain" views together to form a - composite response. The response of the outermost wrapper view will be - returned to the user. The wrapper view will be found as any view is found. - See :ref:`view_lookup`. The "best" wrapper view will be found based on the - lookup ordering. "Under the hood" this wrapper view is looked up via - ``pyramid.view.render_view_to_response(context, request, - 'wrapper_viewname')``. The context and request of a wrapper view is the same - context and request of the inner view. - - If ``wrapper`` is not supplied, no wrapper view is used. + The :term:`view name` of a different :term:`view configuration` which will + receive the response body of this view as the ``request.wrapped_body`` + attribute of its own :term:`request`, and the :term:`response` returned by + this view as the ``request.wrapped_response`` attribute of its own request. + Using a wrapper makes it possible to "chain" views together to form a + composite response. The response of the outermost wrapper view will be + returned to the user. The wrapper view will be found as any view is found. + See :ref:`view_lookup`. The "best" wrapper view will be found based on the + lookup ordering. "Under the hood" this wrapper view is looked up via + ``pyramid.view.render_view_to_response(context, request, + 'wrapper_viewname')``. The context and request of a wrapper view is the same + context and request of the inner view. + + If ``wrapper`` is not supplied, no wrapper view is used. ``decorator`` A :term:`dotted Python name` to a function (or the function itself) which |
