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

Add boat data check to prevent error. #7301

Merged
merged 1 commit into from
Dec 26, 2024

Conversation

Moderocky
Copy link
Member

Description

Fixes a bug with boat data using boat or any boat.

Note to self: remember to merge patch into feature before release.


Target Minecraft Versions: any
Requirements: none
Related Issues: fixes #7300

@Moderocky Moderocky added bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. 2.10 Targeting a 2.10.X version release labels Dec 22, 2024
@Moderocky Moderocky added the feature-ready A PR/issue that has been approved, tested and can be merged/closed in the next feature version. label Dec 22, 2024
@Moderocky Moderocky merged commit 219e358 into SkriptLang:dev/patch Dec 26, 2024
7 checks passed
Moderocky added a commit that referenced this pull request Dec 30, 2024
* 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]>
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 bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. 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.

3 participants