Deprecate outdated utils/validate#6666
Merged
Moderocky merged 4 commits intoMay 8, 2024
Merged
Conversation
Member
|
Isn't there some google validate nonsense inside Bukkit we could use instead. Preconditions, maybe? |
…cate-outdated-utils/validate
Contributor
Author
|
Switched those usages to preconditions |
Moderocky
approved these changes
May 8, 2024
Moderocky
pushed a commit
that referenced
this pull request
May 30, 2024
* Mark Validate as internal * Schedule for removal + change usages * Use preconditions
Moderocky
added a commit
that referenced
this pull request
Jan 1, 2025
* Mark Validate as internal * Schedule for removal + change usages * Use preconditions
erenkarakal
pushed a commit
to erenkarakal/Skript
that referenced
this pull request
Nov 26, 2025
* Mark Validate as internal * Schedule for removal + change usages * Use preconditions
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Technically does change some behaviour (no longer checks for null parameters in some cases) but as these are marked with the NotNull annotation developers should not expect it to work when null gets passed anyways.
I did keep the validation in CommandAliasHelpTopic since it actually checks something that isn't covered by annotations