Deprecate extra ban methods with raw BanEntry#9580
Merged
Machine-Maker merged 1 commit intoMar 3, 2024
Conversation
Machine-Maker
force-pushed
the
fix/deprecate-extra-ban-methods
branch
from
0c13379 to
aa1dbca
Compare
lynxplay
approved these changes
Mar 3, 2024
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.
All these methods use the raw version of BanEntry and have conflicting nullability contracts.
While the raw BanEntry could be fixed, the conflicting nullability contracts would require larger changes that I'm not sure we want to make.