-
Notifications
You must be signed in to change notification settings - Fork 881
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
whitelist -> allowlist and on-chain -> onchain #1131
Conversation
Signed-off-by: Sally MacFarlane <sally.macfarlane@consensys.net>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments.
...ethereum/api/jsonrpc/internal/methods/permissioning/PermRemoveAccountsFromAllowlistTest.java
Outdated
Show resolved
Hide resolved
...su/ethereum/api/jsonrpc/internal/methods/permissioning/PermRemoveNodesFromAllowlistTest.java
Show resolved
Hide resolved
...r/besu/ethereum/api/jsonrpc/internal/methods/permissioning/PermGetAccountsAllowlistTest.java
Outdated
Show resolved
Hide resolved
...r/besu/ethereum/api/jsonrpc/internal/methods/permissioning/PermGetAccountsAllowlistTest.java
Outdated
Show resolved
Hide resolved
...besu/ethereum/api/jsonrpc/internal/methods/permissioning/PermAddAccountsToAllowlistTest.java
Show resolved
Hide resolved
@@ -68,11 +68,11 @@ public JsonRpcResponse response(final JsonRpcRequestContext requestContext) { | |||
} catch (final MultiTenancyValidationException e) { | |||
LOG.error("Unauthorized privacy multi-tenancy rpc request. {}", e.getMessage()); | |||
return new JsonRpcErrorResponse( | |||
requestContext.getRequest().getId(), FIND_ON_CHAIN_PRIVACY_GROUP_ERROR); | |||
requestContext.getRequest().getId(), FIND_ONCHAIN_PRIVACY_GROUP_ERROR); | |||
} catch (final Exception e) { | |||
LOG.error("Failed to fetch on chain privacy group", e); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this message need to be updated?
NODE_WHITELIST_EXISTING_ENTRY(-32000, "Cannot add an existing node to allowlist"), | ||
NODE_WHITELIST_MISSING_ENTRY(-32000, "Cannot remove an absent node from allowlist"), | ||
NODE_WHITELIST_FIXED_NODE_CANNOT_BE_REMOVED( | ||
NODE_ALLOWLIST_NOT_ENABLED(-32000, "Node allowlisting has not been enabled"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"allowlisting" or "allowlist" ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not have a strong opinion on this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok we're deciding that allowlist is a noun not a verb. but changes will come in a new PR
Signed-off-by: Sally MacFarlane <sally.macfarlane@consensys.net>
Signed-off-by: Sally MacFarlane <sally.macfarlane@consensys.net>
Signed-off-by: Sally MacFarlane <sally.macfarlane@consensys.net>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
* whitelist -> allowlist and on-chain -> onchain Signed-off-by: Sally MacFarlane <sally.macfarlane@consensys.net>
Signed-off-by: Sally MacFarlane sally.macfarlane@consensys.net
More internal renames of whitelist -> allowlist
Also changed instances of on-chain -> onchain
See #1108