You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to double check that offensive language has not been intentionally or accidentally (typos, etc) inserted into any of the language files. This rule could check against a list of known offensive words for each language supported by your app, and/or it could also check against a user-supplied list of words to ban.
The check against known offensive words will depend on the communities support, since there would have to be a list like this in the open source words for all the different languages, or the lists would have to be created. In english and in french at least, I know such lists exist.
Alternatively there could be another rule like no-banned-words which could operate only on a user-supplied list of words that they would like to ban across the translation files.
The text was updated successfully, but these errors were encountered:
It would be nice to double check that offensive language has not been intentionally or accidentally (typos, etc) inserted into any of the language files. This rule could check against a list of known offensive words for each language supported by your app, and/or it could also check against a user-supplied list of words to ban.
The check against known offensive words will depend on the communities support, since there would have to be a list like this in the open source words for all the different languages, or the lists would have to be created. In english and in french at least, I know such lists exist.
Alternatively there could be another rule like
no-banned-words
which could operate only on a user-supplied list of words that they would like to ban across the translation files.The text was updated successfully, but these errors were encountered: