[Short-Circuiting The Evaluation While Parsing]

[pbhal]

This PR aims at allowing expression parsing for dynamic evalutaion.

[flotoz]

Hi,
Could you explain why you haven't implemented an EnableException parameter or EnableExceptionAsErrorMessage value from ReSettings for example?
I'm experiencing a regression in my business rule related to exception handling.
This issue is caused by the global catch of ParseException in this implementation.

The global catch is interfering with my expected exception behavior, specifically:

// Act
Action act = () => ConditionInterpretor.Evaluate(expressionToEvaluate);

// Assert
act.Should().ThrowExactly<ParseException>().WithMessage("Unknown identifier 'A'");

How can I have the same behaviour as before ?

Thanks,
Florian

[pbhal]

@flotoz - Valid point. We were evaluating it in terms of whether any parameters which is missing or is short-circuited should evaluate to false, but yes this makes more sense to have a toggle enabled/disabled for exception cascading further. We will keep the default value of this toggle to be true, so that the default behaviour of the library persists forward.
We will be releasing a new version this week. Thanks!