-
Notifications
You must be signed in to change notification settings - Fork 323
[ISSUE#173] fix DLedgerServer The code is not formatted correctly #174
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
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.
Pretty detailed changes. Appreciate it.
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.
Except for compatibility problems, other code is good
public DLedgerStore getdLedgerStore() { | ||
public DLedgerStore getDLedgerStore() { | ||
return dLedgerStore; | ||
} | ||
|
||
public DLedgerRpcService getdLedgerRpcService() { | ||
public DLedgerRpcService getDLedgerRpcService() { | ||
return dLedgerRpcService; | ||
} | ||
|
||
public DLedgerLeaderElector getdLedgerLeaderElector() { | ||
public DLedgerLeaderElector getDLedgerLeaderElector() { | ||
return dLedgerLeaderElector; | ||
} | ||
|
||
public DLedgerConfig getdLedgerConfig() { | ||
public DLedgerConfig getDLedgerConfig() { | ||
return dLedgerConfig; | ||
} |
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.
Directly modifying these interface names will cause compatibility problems
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.
add @deprecated annotation for those methods instead of Directly modifying these interface names. and add a new method like getDLedgerConfig to solution compatibility problems.
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.
Directly modifying these interface names will cause compatibility problems
I search found that RocketMQ uses these methods, and it does cause compatibility issues if you change them directly.add @deprecated annotation for those methods instead of Directly modifying these interface names. and add a new method like getDLedgerConfig to solution compatibility problems.
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.
Directly modifying these interface names will cause compatibility problems
I search found that RocketMQ uses these methods, and it does cause compatibility issues if you change them directly.add @deprecated annotation for those methods instead of Directly modifying these interface names. and add a new method like getDLedgerConfig to solution compatibility problems.
Good idea!
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.
Directly modifying these interface names will cause compatibility problems
I search found that RocketMQ uses these methods, and it does cause compatibility issues if you change them directly.add @deprecated annotation for those methods instead of Directly modifying these interface names. and add a new method like getDLedgerConfig to solution compatibility problems.
Good idea!
I solved the compatibility problem and The code was resubmitted
Fix(173) DLedgerServer The code is not formatted correctly and Correct incorrect words in comment lines