Skip to content
This repository has been archived by the owner on Sep 26, 2019. It is now read-only.

Acceptance Test and DSL rename for IBFT2 #1493

Merged
merged 11 commits into from
May 27, 2019
Merged

Acceptance Test and DSL rename for IBFT2 #1493

merged 11 commits into from
May 27, 2019

Conversation

CjHare
Copy link
Contributor

@CjHare CjHare commented May 24, 2019

PR description

Tech debt, the IBFT suit of tests are actually not testing the Ibft algorithm but the Ibft2 algorithm (related, but not the same). Renaming the AT to avoid any potential confusion about what has / is covered by the AT.

@@ -42,10 +42,10 @@
protected final Blockchain blockchain;
protected final Cluster cluster;
protected final CliqueTransactions cliqueTransactions;
protected final IbftTransactions ibftTransactions;
protected final IbftTwoTransactions ibftTwoTransactions;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two seems like a cop-out - i.e. "I don't want to use "2" so this is the next best" - also generally worried that the word "Transaction" in the DSL is confusing wrt literal Ethereum Transactions ....

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. Ibft2Transactions was the alternative ...however the 2 followed to a capital letter looks a bit funky.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Term transaction can be changed, any suggestions?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually prefer 2 instead of Two

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@@ -109,10 +109,10 @@ public WebSocketConfiguration createWebSocketEnabledConfig() {
}

public JsonRpcConfiguration jsonRpcConfigWithAdmin() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this actually a useful abstraction?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

which part, the JsonRpcConfiguration or the PantheonNodeFactoryUtils?

@@ -42,10 +42,10 @@
protected final Blockchain blockchain;
protected final Cluster cluster;
protected final CliqueTransactions cliqueTransactions;
protected final IbftTransactions ibftTransactions;
protected final IbftTwoTransactions ibftTwoTransactions;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually prefer 2 instead of Two

Copy link
Contributor

@pinges pinges left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are probably aware that there are a few internal variables and fields that still have a "two" in their name ....
I think it is OK, just wanted to make you aware ...

@CjHare
Copy link
Contributor Author

CjHare commented May 27, 2019

Yeah, numbers in packages and classes I'm fine with ...but not in the variables names 😉

@CjHare CjHare merged commit 77feb42 into PegaSysEng:master May 27, 2019
@CjHare CjHare deleted the at-renmaing-ibft branch May 27, 2019 04:01
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants