proto: use MemoPlaintext in TxPlannerRequest #2893
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We overlooked updating the memo field to its type. Fixed now. While I was in there, added some doc strings to make the interfaces abit more intuitive. Still need to follow up with deeper changes to support SwapClaims via the Planner interface; will consult with @aubrika on how best to do that. Refs #2891.
|
These are breaking proto changes. To my eye, looks like the interchaintest work is largely unaffected, given its use of defaults, but the Zpoken folks will need to update. Given that they requested these changes, that's just fine. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We overlooked updating the memo field to its type. Fixed now. While I was in there, added some doc strings to make the interfaces abit more intuitive. Still need to follow up with deeper changes to support SwapClaims via the Planner interface; will consult with @aubrika on how best to do that.
Refs #2891.