Replace use of whitelist with allowlist and blacklist with denylist

Open
#124 2 comments 10 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
api, documentation

Research direction

Search the developer documentation for uses of “whitelist” and “blacklist,” then review the surrounding terminology and any linked guidance. Done means the relevant documentation consistently uses “allowlist” and “denylist”; the issue does not name specific files or tests.

Written by the indexing model from the issue text.

Description

awaiting product change question

I am reading and working with Box API and I have noticed that they refer to blocklist as blacklist and allowlist as whitelist.

Considering a lot of argumentations, besides that those words are racists and we can't even use it as a verb.

Some discussions: https://twitter.com/dhh/status/1032050325513940992.

I think that Box could also follow the good exemples and replace theses terms.

Also:

Regardless of origin, allow/deny are simply clearer terms that does not require tracing the history of black/white as representations of that meaning. We can simply use the meaning directly.

Originally posted by @dhh in https://github.com/rails/rails/issues/33677#issuecomment-414873738

Dominant language
JavaScript
Stars
35
Forks
93
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from box/developer.box.com

All issues in box/developer.box.com

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.