feat: use custom proto messages #87
Draft
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
0xpatrickdev
force-pushed
the
feat/custom-protos
branch
from
911d750 to
ad08790
Compare
0xpatrickdev
force-pushed
the
feat/custom-protos
branch
from
ad08790 to
ce1a17a
Compare
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.
a "works for now" approach that allows developer to bring their own
.protomessages and use them in their contract, until orchestration: example with custom protobuf messages agoric-sdk#10265with feat(cosmos-orch-account): expose
.executeEncodedTxagoric-sdk#10341, developers can send a message like this in a flow with.executeEncodedTx.the large diff is mostly codegen / proto files which were checked in with
chore