-
Notifications
You must be signed in to change notification settings - Fork 70
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
Some default words not censored #21
Comments
What do you think about adding |
@snguyenthanh I think we should, yeah. That will fix the issue for these particular words. We should also display a warning message to let the user know when a words/phrase is invalid and won't be censored. |
I tried adding "!" to
If a swear word ends with a "!", it will be ignored when "!" is an allowed character. Here's a unit test we can use to test punctuation:
|
As of 0.7.0, the words "shi+" and "sh!+" have been added to the default wordlist. But they are not censored. Should we...
ALLOWED_CHARACTERS
(and optionally add "+" toCHARS_MAPPING
for "t").Note that if we go with option 2, profanity separated by "+" (e.g. "fuck+fuck") will no longer be censored.
The text was updated successfully, but these errors were encountered: