-
-
Notifications
You must be signed in to change notification settings - Fork 377
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 expression conversion #7165
Conversation
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.
Will review in depth soon. tud and I discussed some potential issues/edge cases that still need fixed
We need to use conversion whenever there are multiple return types. If the expression does not accept our supertype, then we can attempt to convert it, which will already handle safety checks for multiple return types
This fixes SimpleExpression not converting possible return types that are not contained in the desired types array. For example, if an expression can return a Number or a String, and we want an Expression that is a Number or an World, it will now include converters for String->Number and String->World
I've gone ahead and moved the logic out of SimpleExpression and into ConvertedExpression. This is to preserve the behavior of expressions overriding the method AND that the logic/handling for this is consistent across Skript. The |
* Fix the REMOVE changer of variables (#7163) * Fix the REMOVE changer of variables * Fix wording * Fix tests * Update Variable.java --------- Co-authored-by: sovdee <[email protected]> * Fix Improperly Typed Array in ExprXOf (#7268) * Add boat data check to prevent error. (#7301) * Fix BlockIgniteEvent (#7252) Update BukkitEventValues.java Co-authored-by: Moderocky <[email protected]> * Fix expression conversion (#7165) * Fix expression conversion * Extract duplicate code into a separate helper method * improve conversion strategy * Add .sk to test file * Simplify conversion usage We need to use conversion whenever there are multiple return types. If the expression does not accept our supertype, then we can attempt to convert it, which will already handle safety checks for multiple return types * SimpleExpression: fix possible return type conversion This fixes SimpleExpression not converting possible return types that are not contained in the desired types array. For example, if an expression can return a Number or a String, and we want an Expression that is a Number or an World, it will now include converters for String->Number and String->World * Use safety checks of ConvertedExpression * Remove incorrect converter remake * Move logic from SimpleExpression to ConvertedExpression --------- Co-authored-by: APickledWalrus <[email protected]> Co-authored-by: Efnilite <[email protected]> Co-authored-by: Moderocky <[email protected]> --------- Co-authored-by: _tud <[email protected]> Co-authored-by: sovdee <[email protected]> Co-authored-by: Patrick Miller <[email protected]> Co-authored-by: kyoshuske <[email protected]> Co-authored-by: Efnilite <[email protected]>
Description
This PR fixes an issue where the parser wouldn't attempt to convert an expression if
Expression#canReturn(Class)
returnstrue
. Causing issues when an expression could return a certain type but doesn't once evaluated. For instance, adding two unset variables, which can potentially return variety of types (such as a string), and using the expression in a pattern that expects strings (e.g.,formatted ({_foo} + {_bar})
would result in a stack trace being thrown because the array returned from the arithmetic expression wasn't converted to a string array.Target Minecraft Versions: any
Requirements: none
Related Issues: #7164