Change hooks control (deny_all_hooks_but / allow_all_hooks_but) to be more predictable Prior to this, if one execute code like: with cnx.hooks.deny_all_hooks_but('metadata'): with cnx.hooks.deny_all_hooks_but(): # mycode 'metadata' hooks will be activated anyway in the inner block, which is rather unexpected (of course in real life you only see the latest hooks control statement, the former being higher in the call stack). This is due to the underlying usage of old `enable_hook_categories` / `disable_hook_categories` methods, which were introduced much before the now official context manager based API (with `cnx.[deny|all]_all_hooks_but(...)`). To move on, this patch drop the two legacy methods, rename and privatize related internal state on the connection (`hooks_mode` becomes `_hooks_mode`, `disabled_hook_cats` and `enabled_hook_cats` become `_hooks_categories`) and reimplement the `_hooks_control` context manager to simply update them. See the added unit test for details.

     1

.. _web_module:

     2

     3

:mod:`cubicweb.web`

     4

===================

     5

     6

.. automodule:: cubicweb.web

     7

     8

    Exceptions

     9

    ----------

    10

    11

    .. autoexception:: DirectResponse

    12

    .. autoexception:: InvalidSession

    13

    .. autoexception:: PublishException

    14

    .. autoexception:: LogOut

    15

    .. autoexception:: Redirect

    16

    .. autoexception:: StatusResponse

    17

    .. autoexception:: RequestError

    18

    .. autoexception:: NothingToEdit

    19

    .. autoexception:: ProcessFormError

    20

    .. autoexception:: NotFound

    21

    .. autoexception:: RemoteCallFailed