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.
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
fix(baseapp): hybrid handlers do not drop any #22866
fix(baseapp): hybrid handlers do not drop any #22866
Changes from all commits
5639be0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Ensure Type Safety in
setPointer
Function UsageThe
setPointer
function is used at lines 126, 132, 164, and 170 to replaceproto.Merge
. However, it operates without type or nil checks, which could lead to runtime panics ifdst
andsrc
are nil or of incompatible types.Consider adding type assertions and nil checks to
setPointer
to ensure safe usage. Here's a suggested modification:And update the calls to handle potential errors or panics appropriately.
Also applies to: 132-132, 164-164, 170-170
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.
🛠️ Refactor suggestion
Add Type Checks and Error Handling in
setPointer
FunctionThe
setPointer
function currently lacks type safety and nil checks, which might cause runtime panics if misused.Modify
setPointer
to include type checks and error handling:Ensure that calls to
setPointer
handle the returned error: