-
Notifications
You must be signed in to change notification settings - Fork 597
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
chore: rename SubmitTx
to SendTx
#2255
Conversation
@@ -77,10 +77,10 @@ the associated capability.`), | |||
return cmd | |||
} | |||
|
|||
func newSubmitTxCmd() *cobra.Command { | |||
func newSendTxCmd() *cobra.Command { |
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.
Sorry, this is probably a bit nitpicking, but I was just thinking that what we send to the host chain is a message, right? Or is message and transaction something that mean the same thing? For me I thought that a transaction was the execution of the message, but maybe I am just mistaken... Saying this because maybe this could be renamed to SendMsg
...
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.
I think we should just stick with the naming used in the spec. I see your reasoning but the InterchainAccountPacketData
type may be composed of one or many sdk.Msg
s encoded into the []byte
field.
@@ -25,15 +25,15 @@ func NewMsgServerImpl(keeper *Keeper) types.MsgServer { | |||
} | |||
|
|||
// RegisterAccount defines a rpc handler for MsgRegisterAccount | |||
func (k msgServer) RegisterAccount(goCtx context.Context, msg *types.MsgRegisterAccount) (*types.MsgRegisterAccountResponse, error) { | |||
func (s msgServer) RegisterAccount(goCtx context.Context, msg *types.MsgRegisterAccount) (*types.MsgRegisterAccountResponse, error) { |
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.
Ah, nice I see that you're renaming it here now... So forget about my comment here.
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.
LGTM
* updating naming of submit tx to send tx * use struct embedding (cherry picked from commit a4be561) # Conflicts: # docs/ibc/proto-docs.md # modules/apps/27-interchain-accounts/controller/client/cli/cli.go # modules/apps/27-interchain-accounts/controller/keeper/msg_server.go # modules/apps/27-interchain-accounts/controller/keeper/msg_server_test.go # modules/apps/27-interchain-accounts/controller/types/codec.go # modules/apps/27-interchain-accounts/controller/types/tx.pb.go # proto/ibc/applications/interchain_accounts/controller/v1/tx.proto
* chore: rename `SubmitTx` to `SendTx` (#2255) * updating naming of submit tx to send tx * use struct embedding (cherry picked from commit a4be561) # Conflicts: # docs/ibc/proto-docs.md # modules/apps/27-interchain-accounts/controller/client/cli/cli.go # modules/apps/27-interchain-accounts/controller/keeper/msg_server.go # modules/apps/27-interchain-accounts/controller/keeper/msg_server_test.go # modules/apps/27-interchain-accounts/controller/types/codec.go # modules/apps/27-interchain-accounts/controller/types/tx.pb.go # proto/ibc/applications/interchain_accounts/controller/v1/tx.proto * fix conflicts * chore: fixing test failures Co-authored-by: Damian Nolan <damiannolan@gmail.com> Co-authored-by: crodriguezvega <carlos@interchain.io> Co-authored-by: Cian Hatton <cianhatton@gmail.com>
Description
SubmitTx
rpc toSendTx
msgServer
closes: #2231
Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
docs/
) or specification (x/<module>/spec/
)godoc
comments.Unreleased
section inCHANGELOG.md
Files changed
in the Github PR explorerCodecov Report
in the comment section below once CI passes