-
-
Notifications
You must be signed in to change notification settings - Fork 375
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
Merge patches into feature (before release). #7306
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Fix the REMOVE changer of variables * Fix wording * Fix tests * Update Variable.java --------- Co-authored-by: sovdee <10354869+sovdeeth@users.noreply.github.com>
Moderocky
added
feature-ready
A PR/issue that has been approved, tested and can be merged/closed in the next feature version.
2.10
Targeting a 2.10.X version release
don't merge me !!
For pull requests that should not be merged due to some outstanding dispute, conflict or dependency.
labels
Dec 23, 2024
Efnilite
approved these changes
Dec 23, 2024
Update BukkitEventValues.java Co-authored-by: Moderocky <admin@moderocky.com>
* 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 <apickledwalrus@gmail.com> Co-authored-by: Efnilite <35348263+Efnilite@users.noreply.github.com> Co-authored-by: Moderocky <admin@moderocky.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
2.10
Targeting a 2.10.X version release
don't merge me !!
For pull requests that should not be merged due to some outstanding dispute, conflict or dependency.
feature-ready
A PR/issue that has been approved, tested and can be merged/closed in the next feature version.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bring any last changes from patch (since 2.9.5) onto the feature branch for 2.10.
This has to be done in a funny way because there are a couple of branch conflicts to be manually-resolved.
I think there are a couple of floating PRs on patch currently, so this should be merged after those are complete.