-
-
Notifications
You must be signed in to change notification settings - Fork 36.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
refactor: DRY out usage of isProfane
- Loading branch information
1 parent
e691fed
commit a06a559
Showing
3 changed files
with
18 additions
and
12 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
import { isProfane } from 'no-profanity'; | ||
|
||
import { blocklistedUsernames } from '../../../../shared/config/constants'; | ||
|
||
/** | ||
* Checks if a username is restricted (i.e. It's profane or reserved). | ||
* @param username - The username to check. | ||
* @returns True if the username is restricted, false otherwise. | ||
*/ | ||
export const isRestricted = (username: string): boolean => { | ||
return isProfane(username) || blocklistedUsernames.includes(username); | ||
}; |
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
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