Update feature #41
Open
Update feature #41
Conversation
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
Owner
|
Thanks @arif-rh, I'll have a look at this later today to see if we can get it in. I'm thinking probably as version 2 release feature so that we don't have to have a separate function call. |
Author
|
Yeah, I could understand it. So while waiting the version 2, I have made my version with this feature and also adding whitelist for fixing #21 . Should I closed this? |
|
Typing fuck1 or anything with profane word bypasses the filter. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
cleanWordsto mask only the bad words, not all sentencesActually this
cleanWordscan be implemented to solve issue #20 but to give the backward compability with old version, I make it as new feature