[entity] ensure the .related(entities=False) parameter is honored all the way down (closes #2755994) As of today, such a call will always fill the relation cache by calling .entities() on every single related rset entry. As a consequence, the `limit` parameter handling also had to be fixed. It was bogus in the following ways: * not used in the related_rql, hence potentially huge database requests, but also actually * foolishly used in the .entities()-calling cache routine we now bypass (this changeset ticket's main topic) Now: * we set a limit on the rql expression, and * forbid caching if given a non-None limit (as we don't want to make the cache handling code more complicated than it is already) With this, entity.unrelated gets a better limit implementation (so the code in related/unrelated is nice and symmetric) Risk: * _cw_relation_cache disappears completely, which is good, but this is Python, so you never know ...

     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