-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Rename DBFT Settings #3484
Rename DBFT Settings #3484
Conversation
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, better naming.
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.
This may break 3rd-party apps like neo-express
. But good job. Changes like this for the better.
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.
It seems all other call "Settings".... so maybe keep that way.
We are not sure if the change if fully correct, @cschuchardt88. We just noticed that maybe we need to set a |
Just make a dupe I think the [Obsolete("use DBFTPluginSettings class")]
public ConsensusContext(NeoSystem neoSystem, Settings settings, Wallet wallet) { }
// new way
public ConsensusContext(NeoSystem neoSystem, DBFTPluginSettings settings, Wallet wallet) { } Than in |
I think this will not be a necessary change for now, @cschuchardt88 Later we make this change |
We still need this in several plugins. |
I think that we can make the change to all plugins in the same PR, then we organize this correctly! |
If you want to proceed with this in another PR it will be great. |
Renaming in the same way as other plugins, such as
RpcServerSettings