-
Notifications
You must be signed in to change notification settings - Fork 199
Port Whitelist naming & terms to Allowlist (or alternative) #57
Comments
We do have a meta ticket for this located at apache/cordova#218 but that is abstract. It's good to have a ticket for this repo specifically. |
That's standard with GitHub repo renaming, and even mentioned on the settings for it. I've never had an issue with my own renamed repos. However, the GitHub settings do warn that it could break things, I'm not sure what integration scenarios would be potentially risky or not. |
I'd have to test but I seem to recall the website will redirect but stuff like ssh urls will return with a repo does not exist kind of error. |
AFAIK repos are redirected, username changes are not. |
The plugin is being deprecated and integrated into cordova-android with a new AllowList name apache/cordova-android#1138 So we won't be doing any renaming in this repository |
Feature Request
This is a request to port the
Whitelist
terminology in the name of this repository, code, and documentation, toAllowlist
or another appropriate equivalent.Motivation Behind Feature
Whitelist
though a familiar industry term, is insensitive due to bias, e.g.white == good
.white
is more abstract thanallow
.Allow
is consistent with the operational syntax:<allow-navigation href="http://example.com/*" />
Feature Description
At a glance, it appears to me like most of the changes would be needed in documentation and package naming, though I haven't confirmed this.
A potential challenge is the name of the package and repository itself since that could be a breaking change downstream.
The text was updated successfully, but these errors were encountered: