Collective.behavior.talcondition

Latest version: v1.0.0

Safety actively analyzes 682471 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 3

0.6

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

- Added parameter `empty_expr_is_true` to utils._evaluateExpression than may be True
or False depending that we want an empty expression to be considered True or False.
Previous behavior is kept in utils.evaluateExpressionFor where an empty expression
is considered True. This avoid managing an empty expression in the caller method
[gbastien]

0.5

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

- Added method utils._evaluateExpression that receives an expression
to evaluate, it is called by utils.evaluateExpressionFor. This way, this
method may evaluate a TAL expression without getting it from the `tal_condition`
attribute on the context, in case we want to evaluate arbitrary expression
[gbastien]

0.4

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

- Make the tal_condition field larger (from 30 to 80) for the
AT extender as well as for the DX behavior
[gbastien]
- Added possibility to extend TAL expression context by passing
an `extra_expr_ctx` dict to utils.evaluateExpressionFor, also
integrated to the `evaluate` method of the DX behavior
[gbastien]

0.3

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

- Corrected default value
[sgeulette]
- Little optimization
[sgeulette]

0.2

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

- Added field `role_bypassing_talcondition` to define who can bypass the condition
[anuyens]
- Added translations for new field
[gbastien]

0.1

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

- Initial release.
[IMIO]

Page 3 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.