Consider replacing all the "blacklisting" terminology #317
Closed
sleberknight
started this conversation in
Ideas
Replies: 1 comment
-
I am closing, since it will cause a bunch of work, and is not really a huge problem. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
IntelliJ's code analysis was very adamant that we should replace the "blacklist" terminology throughout the project (its source was the "alex" style guide, which I assume is this one). This would require, at a minimum, deprecating the
BlacklistingConsulFailoverStrategy
and replacing it with a copy of the class with a new name, and then replacing all usages ofBlacklistingConsulFailoverStrategy
.In addition, we would need to find and replace usages in fields, method names, arguments, local variables, etc. which may require more deprecation.
So, assuming we want to do this, what should the new name be?
The Google style guide suggests:
https://developers.google.com/style/word-list#blacklist
I prompted ChatGPT 4 "What are some alternate names for blacklist?" and it gave me a lengthy answer with 10 possibilities. I then asked it to refine using the prompt: "Can you refine this list to the "best" 5 alternatives?" Here is its answer:
Given the general agreement between the Google code style guide and the first three "best" arguments from ChatGPT 4, those are probably the best options.
Beta Was this translation helpful? Give feedback.
All reactions