-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Change name of "whitelist" options to "exclude" options #72
Comments
Whitelist means that we are adding them to the list of checked/good, so they basically aren't checked. You are correct that you could read it the other way around and say that it's something being excluded (not checked). That's an interesting idea to add We can definitely fix up the spelling error asap, I'll open a PR shortly. |
@rootwork I don't see where the |
That is an interesting point; both rationals for |
I agree @SuperKogito, and after thinking over it, I think we should just deprecate the previous @rootwork I still can't find that spelling mistake you are referencing... |
Okay, the changes are done here, #73 ! If you find the spelling error, please open another issue or PR with a link or the fix. Otherwise, thanks for opening the issue! Closing as we've resolved. |
It's confusing that the
white_listed_
inputs for URLs, patterns, and files excludes things rather than including them; usually you'd use the term "whitelist" to describe things you are explicitly including that would otherwise not be included.Additionally, in the output "whitelist" is misspelled for the URL option:
url whitetlist: []
My suggestion would be to change these three input options to
exclude_urls
,exclude_patterns
andexclude_files
, to match theinclude_files
option that already exists. (And also update those values in the output itself.)If you don't want to break existing configs, you could leave the
white_listed_
options as valid along with the new ones, but only list the latter in the docs.The text was updated successfully, but these errors were encountered: