[JEXL-347] Missing unsolvable property exception for reference when used with equals

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.2
• Assignee: Henri Biestro
• Reporter: Cameron Samak
• Created: 25/May/21 00:55
• Updated: 07/Jun/21 13:14
• Resolved: 31/May/21 17:46

Description

I expected

A.B == 5

(with a strict engine and with nothing in the context) to result in an unsolvable property exception, but instead the result was false.

I hit this as part of an attempt to upgrade from 3.0 to a recent snapshot. I think the change in behavior may be related to the addition of ASTEQNode and ASTNENode to isTernaryProtected?

Is it intentional that equal and not equal are handled this way when e.g. greater than or less than are not? If so, is there any option flag that can restore the behavior?