-
Notifications
You must be signed in to change notification settings - Fork 585
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: add ValidateBasic for MsgSendPacket #7468
chore: add ValidateBasic for MsgSendPacket #7468
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.
lgtm, think using errors in chan/v2 would be best but want to see what others say
} | ||
|
||
if len(msg.PacketData) != 1 { | ||
return errorsmod.Wrapf(ErrInvalidPacketData, "packet data must be of length 1, got %d instead", len(msg.PacketData)) |
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.
partially also addreses #7390 (can close it after validation is done for all msgs)
@@ -6,6 +6,7 @@ import ( | |||
sdk "github.com/cosmos/cosmos-sdk/types" | |||
|
|||
clienttypes "github.com/cosmos/ibc-go/v9/modules/core/02-client/types" | |||
channeltypesv1 "github.com/cosmos/ibc-go/v9/modules/core/04-channel/types" |
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.
feels weird mixing these personally? Would prefer if we just moved over all errors (i.e dunno what the error code for this error is? it might conflict with one we define in errors.go
for chan/v2)
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.
We were discussing this with @chatton and thought about importing for now and then having a cleanup issue about moving everything to v2. Though I'm with doing it now if we prefer
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.
perfectly fine with me as long as there's an issue to track it 💪
Description
ref: #7466
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/
).godoc
comments.Files changed
in the GitHub PR explorer.SonarCloud Report
in the comment section below once CI passes.