Releases: hyperjumptech/grule-rule-engine
Releases · hyperjumptech/grule-rule-engine
Release V1.10.2
What's Changed
- [Antlr4] Lexer and parser generation using Antlr4.9 and upgraded antlr4 runtime for to improve performance by @jinagamvasubabu in #249
- Remove rule entry PR by @jinagamvasubabu in #252
Full Changelog: v1.10.1...v1.10.2
Releasing v1.10.1
Releasing patch v1.10.1
- Fix the StrIn() logic bug.
Releasing v1.10.0
Release v1.10.0
- Added Go Embed feature for loading rules from embedded directory for those who uses Go 1.16
- Parser Hardening. which fixes issue #214
Releasing v1.9.1
- Added loading GRL resources from Embedded Directory bundle feature of go 1.16
Releasing v1.9.0
- Ability to store and load
KnowledgeBase
insideKnowledgeLibrary
into binary file (GRB). This makes the loading of rule sets from GRB to be much faster. Almost 10x faster. - Added In function for the string receiver data.
- Engine Listener to know what rule is currently evaluated or executed
- Feature for apps to see GRL script syntax errors.
Releasing patch v1.8.5
Small quick path to fix possible bug when loading RuleSet from binary file,
where io.EOF is not detected causing loading to fail.
Although, by design, this should not be possible.
Releasing v1.8.4
- Added feature to write all rule-sets inside KnowledgeBase into writer (eg. saved into file etc) in binary format (not GRL).
- Read a knowledgebase (previously written as binary) from file directly into KnowledgeLibrary.
Release patch v1.8.3
This patch includes support for UTF-8 character in SIMPLENAME
within the grammar.
With this change, from within the GRL rule name, variable name, function name can
use non-ascii unicode characters except symbols, etc. Thus, golang struct, variables that has unicode in their name
should be accessible from the rule script.
The example/UnicodeRule_test.go
file tested this new patch.
Releasing patch v1.8.2
This patch contains lots of math built-in functions
Check out the Math Function Page
Releasing patch for v1.8.1
- This patch fixes the Floating point literal that fails to parse the numerical digit after a sequence of
.0
rendering12.012
an error.