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
refactor(runtime/v2): untie runtimev2 from the legacy usage of gRPC #22043
refactor(runtime/v2): untie runtimev2 from the legacy usage of gRPC #22043
Changes from 1 commit
80657a5
afc9b06
316578b
2e406ce
4f082de
39633c9
cc9aab4
a79efec
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.
🛠️ Refactor suggestion
Simplify struct initialization and avoid field alignment
Per the Uber Go style guide, aligning struct fields using extra spaces is discouraged. Additionally, explicitly initializing the
err
field tonil
is unnecessary since the zero value of anerror
isnil
.Apply this diff to simplify the struct initialization:
📝 Committable suggestion
Check warning
Code scanning / CodeQL
Iteration over map Warning
Check warning
Code scanning / CodeQL
Iteration over map Warning
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 checks for type assertions in
MakeMsg
andMakeMsgResp
The type assertions in
MakeMsg
andMakeMsgResp
may cause panics if the created instances do not implementtransaction.Msg
. Consider adding checks to handle potential type assertion failures.Apply this diff to safely handle the type assertions:
📝 Committable suggestion
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.
Avoid re-initializing the
handlers
map to prevent overwritingThe
handlers
map is being re-initialized inside theRegisterHandler
method whenevers.error == nil
, which can cause previously registered handlers to be lost. Initialize thehandlers
map only once, preferably when thestfRouterWrapper
is created, or check if it isnil
before initializing.Apply this diff to fix the issue:
📝 Committable suggestion