Feat/profanity filter#164
Conversation
|
@nanaabdul1172 is attempting to deploy a commit to the Abdulazeem's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@nanaabdul1172 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
|
Fix checks |
|
Could you click the Update branch button on your end, or run git pull origin main locally and push? That will make the tests pass so I can merge this!" |
…172/stellar-tags into feat/profanity-filter
- Install bad-words package and initialise Filter at module load - Reject usernames containing restricted words with 400 Bad Request - Mock bad-words in server.test.js and receipts.test.js to fix Jest ESM parse error (badwords-list ships as ESM; Jest runs in CJS mode) - Resolve merge conflicts: take Prisma-based server from remote branch and layer profanity check on top of existing length/secret-key guards
|
Fix backend build test error |
…172/stellar-tags into feat/profanity-filter
|
Please check backend build test error and also fix conflicts |
|
It is still failing, Have you updated the branch ? |
|
Run npm ci This is the build error, update the lock file with npm install |
|
Yes branch is updated
…On Sun, Jun 28, 2026, 11:24 PM Abdulazeem ***@***.***> wrote:
*Abdulazeem-code* left a comment (Abdulazeem-code/stellar-tags#164)
<#164 (comment)>
It is still failing, Have you updated the branch ?
—
Reply to this email directly, view it on GitHub
<#164?email_source=notifications&email_token=BBCOMAS24KVHZU67BJ2SHDL5CGLJPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBSG42TQMZQGY22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4827583065>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BBCOMASB44JDQKBPP6GTLXD5CGLJPAVCNFSNUABGKJSXA33TNF2G64TZHMYTEMZQGI3DGMZWGI5US43TOVSTWNBXGM3TENZQGQ2TDILWAI>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/BBCOMAXSYTNKOURIIBVM4BD5CGLJPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBSG42TQMZQGY22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y>
and Android
<https://github.com/notifications/mobile/android/BBCOMATRGAVYQPFNHNIG3PT5CGLJPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBSG42TQMZQGY22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>.
Download it today!
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
then paste build error code that i just sent to you to your AI to give you the solution to the problem |
|
I have done all that already sir Nothing changed
…On Sun, Jun 28, 2026, 11:28 PM Abdulazeem ***@***.***> wrote:
*Abdulazeem-code* left a comment (Abdulazeem-code/stellar-tags#164)
<#164 (comment)>
then paste build error code that i just sent to you to your AI to give you
the solution to the problem
—
Reply to this email directly, view it on GitHub
<#164?email_source=notifications&email_token=BBCOMASJ4HZNTXPSXWZEJHL5CGLZPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBSG42TSMZVGU4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4827593558>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BBCOMAVGUECEXW67FEPUAW35CGLZPAVCNFSNUABGKJSXA33TNF2G64TZHMYTEMZQGI3DGMZWGI5US43TOVSTWNBXGM3TENZQGQ2TDILWAI>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/BBCOMASN2PBLNKXFUEZEGAT5CGLZPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBSG42TSMZVGU4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y>
and Android
<https://github.com/notifications/mobile/android/BBCOMAUNIXUYE6OOGBJYAAT5CGLZPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBSG42TSMZVGU4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>.
Download it today!
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
2 participants
closes #95
Implementation Complete ✓
The profanity filter has been successfully added to the /register route in server.js. Here's what was implemented:
Changes Made:
Package Installation: The bad-words package was already installed in the project
Filter Initialization: Added the filter at the top of the route handler:
const Filter = require('bad-words');
const filter = new Filter();
Validation Logic: Added profanity check after basic field validation but before database operations:
// Extract the username part before the * for profanity check
const usernameOnly = username.split('*')[0];
if (filter.isProfane(usernameOnly)) {
return res.status(400).json({ error: 'Username contains restricted words' });
}
How It Works:
The filter checks only the username portion (before the * domain separator)
If profanity is detected, the request is rejected with a 400 Bad Request status
The error message returned is: "Username contains restricted words"
Valid usernames proceed through the normal registration flow
Testing Recommendations:
You can test this by attempting to register with profane usernames. The filter will catch common offensive words and prevent registration, keeping your federation directory professional and compliant.