-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
TXM In-memory: step 3-02-CreateTransaction #12181
TXM In-memory: step 3-02-CreateTransaction #12181
Conversation
I see that you haven't updated any CHANGELOG files. Would it make sense to do so? |
Quality Gate passedIssues Measures |
return txmgrtypes.Tx[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]{}, nil | ||
tx := txmgrtypes.Tx[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]{} | ||
if ms.chainID.String() != chainID.String() { | ||
panic("invalid chain ID") |
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.
Nit: Might be useful to improve these error messages across all functions in case the panic occurs. Something like the following?
panic("invalid chain ID") | |
panic(fmt.Sprintf("invalid chain ID: expected %s but recieved %s", ms.chainID.String(), chainID.String()) |
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.
linked this in #12176 so we can address it to the other panics as well
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.
Looks good, small nit about panic messages
NOTES:
Parent PR: