From 888dedaf533b4895f22cc5cc328f9bc0cffcea85 Mon Sep 17 00:00:00 2001
From: Mahmoud Ben Hassine <mbenhassine@pivotal.io>
Date: Sun, 19 Apr 2020 14:31:20 +0200
Subject: [PATCH] Add comment about why MVEL.evalToBoolean is not used in
 MVELCondition

---
 .../src/main/java/org/jeasy/rules/mvel/MVELCondition.java        | 1 +
 1 file changed, 1 insertion(+)

diff --git a/easy-rules-mvel/src/main/java/org/jeasy/rules/mvel/MVELCondition.java b/easy-rules-mvel/src/main/java/org/jeasy/rules/mvel/MVELCondition.java
index c6f339e..a2ed706 100644
--- a/easy-rules-mvel/src/main/java/org/jeasy/rules/mvel/MVELCondition.java
+++ b/easy-rules-mvel/src/main/java/org/jeasy/rules/mvel/MVELCondition.java
@@ -60,6 +60,7 @@ public class MVELCondition implements Condition {
 
     @Override
     public boolean evaluate(Facts facts) {
+        // MVEL.evalToBoolean does not accept compiled expressions..
         return (boolean) MVEL.executeExpression(compiledExpression, facts.asMap());
     }
 }