feat(automod): refactor slur processing #886
Open
Conversation
This file contains 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
devankestel
approved these changes
Dec 22, 2024
|
this looks interesting/promising, but it will probably be January (2025) before we can take a real look |
Enjoy your holiday break! There's no urgency, this is just maintainability of future badword detection rather than any urgent need to add more badwords. |
|
Welcome back, happy new year @bnewbold |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The old automod code relied upon cut-pasting a bunch of
[hhhhhh][eeeeeee][iiiiiiil]{2}[oooooooooo0]strings around when the regexes could be a lot more readable by separating the unicode substitution and badword checking steps. This attempts to unify the code into one place.