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

CSS Coding Standards

     2

--------------------

     3

     4

(Draft, to be continued)

     5

     6

:Naming: camelCase

     7

     8

Indentation rules

     9

~~~~~~~~~~~~~~~~~

    10

- 2 espaces avant les propriétés

    11

    12

- pas d'espace avant les ":", un espace après

    13

    14

- 1 seul espace entre les différentes valeurs pour une même propriété

    15

    16

    17

Documentation

    18

~~~~~~~~~~~~~

    19

Please keep rules semantically linked grouped together, with a comment about

    20

what they are for.

    21

    22

Recommendation

    23

~~~~~~~~~~~~~~

    24

- Try to use existing classes rather than introduce new ones

    25

    26

- Keep things as simple as possible while in the framework

    27

    28

- Think about later customization by application

    29

    30

- Avoid introducing a new CSS file for a few lines of CSS, at least while the

    31

  framework doesn't include packing functionalities

    32

    33