Improve option naming

[sindresorhus]

I don't think we should use whitelist/blacklist type naming. They have negative connotations for some.

whitelist => allowList
blacklist => denyList

This applies to:

• blacklist option in no-keyword-prefix
• whitelist option in prevent-abbreviations
• extendDefaultWhitelist option in prevent-abbreviations

---

I'm not really interested in discussing the merits of this. It's the right thing to do.

https://thenextweb.com/dd/2020/07/13/linux-kernel-will-no-longer-use-terms-blacklist-and-slave/

[fisker]

Rename default branch to main?

[sindresorhus]

Rename default branch to main?

GitHub promised they would come with a feature to automate this, so I'm waiting for that.

[fregante]

Why List? It could just be allow/deny, include/exclude, etc

Or something even more appropriate than a generic whitelist/blacklist equivalent:

• prevent-abbreviations: except/allowed
• no-keyword-prefix: keywords (i.e. the keywords that are not allowed)

[sindresorhus]

@fregante That was just the recommended replacement when I read about it.

---

prevent-abbreviations: except/allowed

Yeah, allowed would work there. What would extendDefaultWhitelist be then?

no-keyword-prefix: keywords (i.e. the keywords that are not allowed)

👍

[fregante]

Not as clear probably, but

• extendDefaultList
• extendDefaultAllowedList
• extendDefaults

[sindresorhus]

extendDefaultList
extendDefaultAllowedList

Why *List? 😛

[fisker]

When I send #1164, I forgot this issue, allowed was suggested for prevent-abbreviations, but I guess allowList is fine.