-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: trigger condition cache expressions correctly #3357
Conversation
Pull Request Test Coverage Report for Build 620406469
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All looks good to me. Was this an issue found during Composer testing?
} | ||
|
||
return Expression.andExpression.apply(Expression, expressions); | ||
return Expression.andExpression(...expressions); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
No, I was porting #3320 and found that we have not ported the latest getExpression/createExpression changes from C#. |
Fixes #3356
Description
OnCondition.getExpression() was caches the root expression, but all of the children which override getExpression() were not. This means all child conditions which overrode getExpression() were calling Expression.parse() on EVERY call.
Specific Changes
Testing