Skip to content
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 word usage: whitelist -> allowlist #35

Closed
ttsukagoshi opened this issue Nov 20, 2022 · 0 comments · Fixed by #67
Closed

Change word usage: whitelist -> allowlist #35

ttsukagoshi opened this issue Nov 20, 2022 · 0 comments · Fixed by #67
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Milestone

Comments

@ttsukagoshi
Copy link
Owner

Avoid using words that some readers may find offensive.

This will involve changing command options:

axe-scan run --whitelist whitelistFileName
axe-scan summary --whitelist whitelistFileName

to

axe-scan run --allowlist allowlistFileName
axe-scan summary --allowlist allowlistFileName

and the relevant parts of README as well.

Subsequent v1.x versions will switch to the allowlist terminology while keeping the -W | --whitelist options available. These original options shall be deprecated in v2.0 and after.

@ttsukagoshi ttsukagoshi added documentation Improvements or additions to documentation enhancement New feature or request labels Nov 20, 2022
@ttsukagoshi ttsukagoshi self-assigned this Nov 20, 2022
@ttsukagoshi ttsukagoshi added this to the v1.2.0 milestone Nov 20, 2022
@ttsukagoshi ttsukagoshi modified the milestones: v1.2.0, v2.0 Nov 20, 2022
ttsukagoshi added a commit that referenced this issue Jan 13, 2023
Users can use the allowlist option instead,
which is identical to what whitelist option did.
Full implementation of #35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant