Added a profanity #1
Conversation
Added a profanity that was introduced in a South Park (TV series) episode about curse words.
There was a problem hiding this comment.
Hi @randolf, thanks for the contribution!
The .json files are the source of truth and build out the corresponding .txt files after running ./bin/build.js
If you're happy with your changes to en.json, you can run the build script and it will generate the desired en.txt file for it.
| @@ -2477,6 +2477,10 @@ | |||
| "id": "horseshit", | |||
| "match": "horseshit|horse-shit|horse shit" | |||
| }, | |||
| { | |||
| "id": "meecrob", | |||
| "match": "pile of meecrob" | |||
There was a problem hiding this comment.
This JSON takes pipe-separated values for the match attribute and will turn those into individual items in the en.txt list; the id attribute value isn't added to the .en.txt list from this though.
Based on your original change to en.txt, this would instead be:
| "match": "pile of meecrob" | |
| "match": "meecrob" |
Otherwise, if you wanted to see the full match for either/or you could use:
| "match": "pile of meecrob" | |
| "match": "meecrob|pile of meecrob" |
Though just defining meecrob for the match would probably result in the desired behaviour for most implementations using this list, e.g. piece of meecrob -> piece of *******
Added a profanity that was introduced in a South Park (TV series) episode about curse words.