-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[ISSUE #1484]♻️Refactor create MQBrokerErr replace with client_broker_err! macro🔥 #1486
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
💡 Codebase verification
Inconsistent error handling pattern found - some instances still use direct constructor
The verification revealed that there are still 4 instances in
mq_client_api_impl.rs
whereMQBrokerErr
is being created directly instead of using theclient_broker_err!
macro. These instances should be refactored for consistency:MQBrokerErr::new_with_broker
in SendStatus match blockMQBrokerErr::new_with_broker
in another match blockMQBrokerErr::new_with_broker
in response code checkMQBrokerErr::new_with_broker
in LockBatchResponseBody decode error handling🔗 Analysis chain
Consistent refactoring of error handling using the new macro.
The replacement of direct
MQBrokerErr
creation with theclient_broker_err!
macro has been consistently applied across all error handling cases. This refactoring:Let's verify that all instances of
MQBrokerErr
creation have been replaced:Also applies to: 779-783, 870-874, 970-974, 1037-1041, 1068-1072, 1108-1112, 1151-1155, 1158-1162, 1222-1226, 1308-1312
Let me check the remaining instances of direct
MQBrokerErr
creation in the implementation file to verify if they should be using the macro.🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 1604
Script:
Length of output: 1486