Collective.behavior.talcondition

Latest version: v0.14

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

Scan your dependencies

Page 2 of 3

0.10

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

- Do not break if parameter `expression` passed to
`utils._evaluateExpression` is None.
[gbastien]

0.9

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

- Added new parameter `error_pattern=WRONG_TAL_CONDITION` to
`utils.evaluateExpressionFor` and underlying `utils._evaluateExpression` to
be able to log a custom message in case an error occurs during
expression evaluation.
[gbastien]

0.8

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

- Mark elements using behavior with `ITALConditionable` interface so it behaves
like element using the AT extender.
[gbastien]

0.7

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

- Use CheckBoxWidget for `ITALCondition.roles_bypassing_talcondition` to ease
selection when displaying several elements.
[gbastien]

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]

Page 2 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.