[hooks/security] allow edition of attributes with permissive permissions
If an attribute has more permissive security rules than the entity
type itself, we should be green and not deny action because of an
early global entity permission check (with the more restrictive
rules).
Only if one attribute with the entity-level permission rules is edited
will the global check be performed.
Note:
* the "if action == 'delete'" check at the entry of
check_entity_attributes is a guard for a condition currently not
happening in cubicweb itself (but application hooks could
conceivably call this function with a 'delete' action)
Closes #3489895.
CSS Coding Standards
--------------------
(Draft, to be continued)
:Naming: camelCase
Indentation rules
~~~~~~~~~~~~~~~~~
- 2 espaces avant les propriétés
- pas d'espace avant les ":", un espace après
- 1 seul espace entre les différentes valeurs pour une même propriété
Documentation
~~~~~~~~~~~~~
Please keep rules semantically linked grouped together, with a comment about
what they are for.
Recommendation
~~~~~~~~~~~~~~
- Try to use existing classes rather than introduce new ones
- Keep things as simple as possible while in the framework
- Think about later customization by application
- Avoid introducing a new CSS file for a few lines of CSS, at least while the
framework doesn't include packing functionalities