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
Remove IBC logic from x/upgrade #8673
Remove IBC logic from x/upgrade #8673
Changes from 10 commits
e65921b
64b59fd
1234383
c5c0d26
31ca56d
9ea85b8
3449f66
01cc2d7
975133b
21fb511
862dc37
1d5bdd5
dd180e8
99f8a76
973cef5
c47f4ce
c9e515b
1590837
a2959f6
5295e58
b136626
49924c8
d05fba1
d86f0b0
96bc1c8
28fb256
b1fc663
715dd42
2b2e0b0
a0ff9e3
7b281f4
75edb27
d771d4f
e9597c1
07670fc
d3ecf9e
2a6adb0
0b51095
d40e695
7906b28
0404d4e
9dbcbe1
73fefb9
abc4ebb
95cb360
5e20b2f
57f2c8d
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.
This is proto-breaking. Could we just add a new field instead? Or else we can also bump to v1beta2
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 can do whichever you prefer. The old fields would just be unused if I added a new field. It would also be unusable since I cannot fulfill the
UnpackInterfaces
function since there won't be a interface to unpack into. I presume I'd have to change this for the Upgrade Plan as well or does only the Query definitions matter?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.
Not bumping to v1beta2 would be ideal. If the old field is not used anymore, I would say let's go for
reserved
, like hereSee https://developers.google.com/protocol-buffers/docs/proto#updating
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.
sweet, thanks for catching this. Updated it, let me know if anything is wrong
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.
The proto-breakage check still says breaking, but I presume this is fine?
Do I need the
reserved "option";
part?