-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
feat: replace insensitive terms #1522
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1522 +/- ##
=======================================
Coverage 99.92% 99.92%
=======================================
Files 96 96
Lines 1286 1289 +3
=======================================
+ Hits 1285 1288 +3
Misses 1 1
Continue to review full report at Codecov.
|
Respectively I have to turn this down. Personally I have very strong view on this issues -- changing names is such a cosmetic approach to solving this issue. But yes, black lives matter. /cc. @chriso |
However, please feel free to contribute this project on the other open issues, welcome! Thanks for the PR. |
Sure, changing names is just a cosmetic approach, but because the most of major companies like Apple and Microsoft and even Babel are deprecating old names, wouldn't it be a good idea to follow this new "standard"? |
This PR replaces all those terms considered insensitive and racist.
Nothing of what is contained in this pull request is a breaking change.
Particularly it tackles:
blacklist
andwhitelist
sanitizersisWhitelisted
validatorisURL
andisEmail
optionsChecklist