Skip to content

Releases: zeroSteiner/rule-engine

Release v3.5.1

Choose a tag to compare

@github-actions github-actions released this 25 Feb 19:33
v3.5.1
Version 3.5.1

Release v3.5.0

Choose a tag to compare

@zeroSteiner zeroSteiner released this 30 Jul 22:03
v3.5.0

Version 3.5.0

Release v3.4.0

Choose a tag to compare

@zeroSteiner zeroSteiner released this 12 Jul 22:28
v3.4.0

Version 3.4.0

Release v3.3.1

Choose a tag to compare

@github-actions github-actions released this 20 Aug 00:08
v3.3.1
Version 3.3.1

Release v3.3.0

Choose a tag to compare

@github-actions github-actions released this 20 Jul 23:48
v3.3.0
Version 3.3.0

Release v3.2.0

Choose a tag to compare

@github-actions github-actions released this 03 Apr 18:19
v3.2.0

Version 3.2 adds support for array comprehension expressions (like Python's list comprehension), for example [ member for member in iterable if member ]. Additionally, the rule_engine.ast module has also been refactored to move the data type definitions into the dedicated rule_engine.types module. Finally, the two resolution errors now specify suggestions (when able) to help users correct common mistakes such as typos.

Release v3.1.2

Choose a tag to compare

@github-actions github-actions released this 31 Mar 23:09
v3.1.2
Version 3.1.2

Release v3.1.1

Choose a tag to compare

@github-actions github-actions released this 19 Mar 23:36
v3.1.1
Version 3.1.1

Release v3.1.0

Choose a tag to compare

@github-actions github-actions released this 15 Mar 23:25
v3.1.0

Version 3.1 adds the new SET data type which supports (among other things) checking for intersections via the bitwise and operator (&).

Release v3.0.0

Choose a tag to compare

@github-actions github-actions released this 02 Mar 00:45
v3.0.0

Version 3.0 switches the Rule Engine FLOAT data type to using Python's decimal.Decimal internally instead of float. The if, elif, else, for and while keywords are also reserved for future use now, they may not be used as symbol / variable names.

The rule_engine.ast module is also now documented as being private. Downstream projects should not reference it directly because the API may change between minor version releases in order to add new functionality.