You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rules can be evaluated both in the engine's ExecuteWithContext()/Execute() function and inside of FindMatchingRules(), but listeners are only triggered in the Execute() call.
It'd be helpful if notifyEvaluateRuleEntry were added to FindMatchingRules() to trigger EvaluateRuleEntry listeners when FindMatchingRules() is called.
My motivation for this is to be able to get the rule names affected when FindMatchingRules() returns an error during processing of a rule like I'd do with a listener for Evaluate().
The text was updated successfully, but these errors were encountered:
corylation
added a commit
to corylation/grule-rule-engine
that referenced
this issue
Jul 13, 2023
Rules can be evaluated both in the engine's
ExecuteWithContext()
/Execute()
function and inside ofFindMatchingRules()
, but listeners are only triggered in theExecute()
call.It'd be helpful if
notifyEvaluateRuleEntry
were added toFindMatchingRules()
to triggerEvaluateRuleEntry
listeners whenFindMatchingRules()
is called.My motivation for this is to be able to get the rule names affected when
FindMatchingRules()
returns an error during processing of a rule like I'd do with a listener forEvaluate()
.The text was updated successfully, but these errors were encountered: