-
Notifications
You must be signed in to change notification settings - Fork 20.3k
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
cmd/geth: rename --whitelist to --eth.requiredblocks #24505
Conversation
|
I agree that the peer prefix is new, but feel like requiredblocks by itself
still suffers some of the same issues as the old name: it’s still unclear
which subsystem requires these blocks from who. peerrequiredblocks (no dot
namespace) is very hard to parse especially with the double r.
I’m willing to move forward with requiredblocks though if others feel it’s
clear enough.
…On Sun, Mar 6, 2022 at 3:59 AM Felix Lange ***@***.***> wrote:
requiredblocks is a very good name. I don't really agree with the peer.
prefix because we don't have any other flag like that.
—
Reply to this email directly, view it on GitHub
<#24505 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAANCEFF5GNBMSLXGXTVO6TU6SMYNANCNFSM5P6R4HAA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I think it's good to have |
I just want something other than |
Yeah I'm fine with skipping the |
We have now settled on |
* cmd, eth: Rename whitelist argument to peer.requiredblocks * eth/ethconfig: document PeerRequiredBlocks better * cmd/utils: rename new flag to --eth.requiredblocks Co-authored-by: Felix Lange <fjl@twurst.com>
* cmd, eth: Rename whitelist argument to peer.requiredblocks * eth/ethconfig: document PeerRequiredBlocks better * cmd/utils: rename new flag to --eth.requiredblocks Co-authored-by: Felix Lange <fjl@twurst.com>
* cmd, eth: Rename whitelist argument to peer.requiredblocks * eth/ethconfig: document PeerRequiredBlocks better * cmd/utils: rename new flag to --eth.requiredblocks Co-authored-by: Felix Lange <fjl@twurst.com>
For awhile now I've wanted to rename the "whitelist" option I introduced in #18028 to something both more descriptive (the current flag does not convey what is being whitelisted) and more inclusive.
IMO
--peer.requiredblocks
is much more self-documenting, though I'm totally open to having a discussion around other argument names (and will make the required changes to this PR if we decide on a different name).