-
Notifications
You must be signed in to change notification settings - Fork 45
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
Wrong detection #19
Comments
Hey @olezhkafp did you ever figure out a fix for this? We are facing this issue as well |
Hello sorry for the issue. Could we perhaps remove this word from the blocked list? I have no idea about that language but looks odd |
@Darthmaul Yes, we care copied the json file with the bad words, modified it and use instead of basic one. |
@ConsoleTVs yes, looks like this is some issue and not the bad word. I think "13." can not be some bad word) |
Hey guys, care to test version |
I know this is solved, but I'd just like to add a guess here: |
Hi. for example we have string like this:
$value = '<p><span style="color: rgb(246,139,106);">Lauren J.</span>, Hi</p>';
In this case 139 will be replaced as *** because:
Profanity::blocker(trim($value))->badWords() detects the bad word:
Is it possible to fix? as '139' != '13.'
The text was updated successfully, but these errors were encountered: