Skip to content

Use proper deprecation warning for ExprNoDamageTicks #7890

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

Conversation

APickledWalrus
Copy link
Member

Problem

ExprNoDamageTicks is deprecated, but it does not print a "proper" deprecation warning. Thus, it is not affected by suppressing those warnings. It also spams the tests a lot.

Solution

I switched to the proper method from ScriptWarning. The warning itself remains the same.

Testing Completed

I did suppress the warning for the existing test script and confirmed that it is no longer printed.

Supporting Information

n/a


Completes: none
Related: none

@APickledWalrus APickledWalrus requested a review from a team as a code owner May 22, 2025 20:55
@APickledWalrus APickledWalrus requested review from Efnilite and erenkarakal and removed request for a team May 22, 2025 20:55
@APickledWalrus APickledWalrus added bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. enhancement Feature request, an issue about something that could be improved, or a PR improving something. labels May 22, 2025
@skriptlang-automation skriptlang-automation bot added the needs reviews A PR that needs additional reviews label May 22, 2025
@skriptlang-automation skriptlang-automation bot added patch-ready A PR/issue that has been approved and is ready to be merged/closed for the next patch version. and removed needs reviews A PR that needs additional reviews labels May 22, 2025
@APickledWalrus APickledWalrus merged commit 3e4106b into SkriptLang:dev/patch May 23, 2025
5 checks passed
@APickledWalrus APickledWalrus deleted the patch/better-no-damage-ticks-warning branch May 23, 2025 00:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. enhancement Feature request, an issue about something that could be improved, or a PR improving something. patch-ready A PR/issue that has been approved and is ready to be merged/closed for the next patch version.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants