Tags: fivezh/grule-rule-engine
Tags
Draft Remove rule entry PR (hyperjumptech#252) * Fix for String In issue * added check for isvalid condition * removed extra nil check and len check * Antlr4.9 and go runtime changes * Update ANTLR.md * updated with review comments * remove rule entry changes * removing rule entry from knowledgebase library * added comments * updated with review comments * updated go.mod * Added UUID import
Chore/readme (hyperjumptech#243) * Added performance test * Fix linting * README.md * make the image background transparent
Check all interface conversion in the parser and abort if a failure o… …ccurs (hyperjumptech#216) * When Presented with syntactically incorrect rules, the parser may generate a panic when attempting to type case an AST element. If this occurs, the panic may propagate to third party code resulting in an application crash. * All type casts are now done safely and are checked for success. If a cast fails, parsing is aborted by setting StopParse to true and returning immediately. This allows ANTLR to return a syntax error to the caller. * A new test has been added to validate that the parser will not crash when presented with invalid rule input. The test cases have been designed specifically to mis-use GRL keywords as well as misplace otherwise correct keywords within a rule. Co-authored-by: Niall Newman <[email protected]>
Feat/bettertest (hyperjumptech#195) * Added new ErrorReporter to store all grule's GRL parsing errors * Updated README.md to removed featured product and added comment in the GrlParseErrorDetection_test.go so reader can easily understand how to use ErrorReporter * Added in function * Added lots of documentations of new features * Fixing linting issue for GruleEngineListener * Fix very minor logic bug * avoiding go mod tidy issue golang/go#44557 that CI pipeline to fail
PreviousNext