Skip to content
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 9 commits into from
Dec 30, 2024

Conversation

Moderocky
Copy link
Member

@Moderocky Moderocky commented Dec 23, 2024

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.

UnderscoreTud and others added 2 commits December 14, 2024 19:24
* Fix the REMOVE changer of variables

* Fix wording

* Fix tests

* Update Variable.java

---------

Co-authored-by: sovdee <10354869+sovdeeth@users.noreply.github.com>
@Moderocky 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
@Moderocky Moderocky self-assigned this Dec 23, 2024
@Moderocky Moderocky marked this pull request as ready for review December 23, 2024 13:19
Moderocky and others added 6 commits December 23, 2024 18:21
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>
@Moderocky Moderocky merged commit c01fc90 into dev/feature Dec 30, 2024
7 checks passed
@Moderocky Moderocky deleted the feature/pre-merge-patch branch December 30, 2024 06:50
@Moderocky Moderocky restored the feature/pre-merge-patch branch December 30, 2024 06:55
@Efnilite Efnilite deleted the feature/pre-merge-patch branch January 1, 2025 23:33
@Efnilite Efnilite restored the feature/pre-merge-patch branch January 1, 2025 23:33
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants