-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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(x/tx): Harmonize TypeResolver interface #16846
Conversation
@@ -31,13 +31,16 @@ Ref: https://keepachangelog.com/en/1.0.0/ | |||
|
|||
## [Unreleased] | |||
|
|||
## v0.9.0 |
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'll be tagging v0.9.0 of x/tx
after this PR.
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, I'll probably wait for this to be fixed before tagging: #16521 (comment) forgot about this.
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.
changes are looking good
Is the failing tx test addressed as part of another PR or this PR ?
It is broken in another PR (see #16846 (comment)) |
@@ -14,6 +14,11 @@ import ( | |||
"cosmossdk.io/core/address" | |||
) | |||
|
|||
type TypeResolver interface { |
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.
should we put this in core and import it everywhere so we dont have the same issue in the future
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 am uncertain if its worth adding an extra package in core for that. Not sure how we would even name it.
However, if you have a proposition, I am not against it.
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.
left one question otherwise LGTM
Description
The
TypeResolver
interface is different inx/tx
than in the rest of the codebase (orm and client/v2).cosmos-sdk/orm/model/ormtable/build.go
Lines 64 to 67 in c7270e8
cosmos-sdk/client/v2/autocli/flag/builder.go
Lines 15 to 18 in c7270e8
This PR harmonize it.
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
to the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!
in the type prefix if API or client breaking change