Releasing v1.10.5

• Adding new built in function MatchString for matching a string to regular expression. fixes issue #281
• A way to track the cause of panic when importing GRB rule binary file. Right now, when the process raises a panic, a panic log were emitted but without showing panic message and the error message were not returned. Now the panic message were displayed in the log and the error returned.

Releasing v1.10.4

• Minor fix where when using JSON as data into the context, when evaluation is evaluating JSON path beyond the JSON data it self, the evaluation yield a panic. Now evaluating JSON data in context will not panic but instead the rule entry will simply failed the evaluation and rule execution proceed normaly.
• Minor broken link fix in the documentation

Releasing v1.10.3

• Add option to error on failed grule engine execution
• Fixed #268 : Where everytime engine execute using the same knowledgebase instance, the rule entries are not resetted as intended.

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 inside KnowledgeLibrary 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.