-
-
Notifications
You must be signed in to change notification settings - Fork 526
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
Editorial: consider offering alternative to whitelist_externals #1491
Labels
Comments
We cannot do this without breaking backwards compatibility. We might be able to add other aliases for this setting as part of #1394, ETA at least September. |
Can an alias be provided in the meantime? |
Merged
4 tasks
PRs are welcome. |
kennknowles
added a commit
to kennknowles/beam
that referenced
this issue
Jun 22, 2020
…possible For context, see: - https://tools.ietf.org/html/draft-knodel-terminology-01 - https://developers.google.com/style/inclusive-documentation#features-and-users Blocked by configuration of other projects and vendored code: - tox-dev/tox#1491 - jenkinsci/ghprb-plugin#784 - Generated storage_v1_messages.py (undocumented how we generated this!?) - Many golang vendored modules
@dajose thank you! |
This is now released with 3.18.0 |
yirutang
pushed a commit
to yirutang/beam
that referenced
this issue
Jul 23, 2020
…possible For context, see: - https://tools.ietf.org/html/draft-knodel-terminology-01 - https://developers.google.com/style/inclusive-documentation#features-and-users Blocked by configuration of other projects and vendored code: - tox-dev/tox#1491 - jenkinsci/ghprb-plugin#784 - Generated storage_v1_messages.py (undocumented how we generated this!?) - Many golang vendored modules
3 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Using whitelist (and its counterpart) isn't exactly welcoming. While migrating away from it entirely might be hard due to compatibility considerations, it'd be nice if configuration files from projects that build on this technology could avoid it.
See https://tools.ietf.org/html/draft-knodel-terminology for additional context.
The text was updated successfully, but these errors were encountered: