mirror of
https://github.com/wiremock/WireMock.Net.git
synced 2026-01-11 14:20:29 +01:00
Change "blacklist" and "whitelist" terms #285
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @akamud on GitHub (Jul 18, 2020).
Originally assigned to: @StefH on GitHub.
Is your feature request related to a problem? Please describe.
These terms have proven not to be inclusive to all people in IT. A lot of big projects are already moving away from them. There are better terms that describe the intention of these lists more clearly too.
Describe the solution you'd like
A lot of repos are changing the "blacklist" term to "denylist" or "blocklist", and "whitelist" to "allowlist" or "passlist". Deny/Allow seems to be more common, though.
I know this would be a breaking change, so maybe a minor release marking these objects as
Obsoletewhile providing the new Allow/Denylists could make this less traumatic for a possible future major release?@StefH commented on GitHub (Jul 19, 2020):
In WireMock.Net, I have only used the following:
https://github.com/WireMock-Net/WireMock.Net/blob/master/src/WireMock.Net/Settings/IProxyAndRecordSettings.cs#L41
So I guess renaming it to:
ExcludedHeadersandExcludedCookieswould be fine.@akamud commented on GitHub (Jul 19, 2020):
Seems fine to me, the new names are more explicit too. Other than that, I just found some references for Whitelist and Blacklist in
infura.yaml, not sure what are those.@StefH commented on GitHub (Jul 19, 2020):
Infura.yaml is just an third party example openapi yaml specification file.