-
Notifications
You must be signed in to change notification settings - Fork 286
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
Deprecate the use of words Whitelist and Blacklist #690
Comments
Hi @dschveninger, thanks for filling the issue. Changing all internal declarations and references to
Please let me know if you are OK with the approach. |
I agree with the steps. We will review the steps and submit a PR. Thank you. |
@dschveninger do you want to move forward opening a PR? I'd love to make this change happen. |
Hi @dschveninger any suggestions/alternatives to thouse words, that we can prepare some commits in this topic? |
hey @chavacava any next steps/plans/suggestions with this issue? |
Hi @mfederowicz if you plan to go ahead with the renaming, your PR are welcome. That said, the next phase of refactoring might imply breaking changes. Thus, before putting some effort on coding, please open a thread to discuss. |
ok i think that we can close this issue, latest changes removed usage of Whitelist and Blacklist Whitelist https://github.com/mgechev/revive/search?q=whitelist as you can see there is only one usage of phrase "imports-blacklist" it is only for fix/resolve breaking changes |
Overview
The words whitelist and blacklist been used for years, but with current events we are questioning if we could some more inclusive terms.
Question
I was wonder if you would be opposed to deprecating the use of the words blacklist and whitelist in this repository?
Suggestion
I would like to get feed back on either addressing the whole repo
Whitelist https://github.com/mgechev/revive/search?q=whitelist
Blacklist https://github.com/mgechev/revive/search?q=blacklist
Or just address it with the rules naming and config words. The approach is to mirror the old config with a new config. The old config would echo out a deprecation message for a future version.
Config changes https://github.com/mgechev/revive/blob/a67ecdd7ba96272124152b280054d16368e774ac/config/config.go
if you are not opposed to the idea, I may have someone that can address this. I just wanted to get your feedback first before we would submit a PR.
The text was updated successfully, but these errors were encountered: