Skip to content
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

Example of parsing SubMessage data field #509

Closed
ethanfrey opened this issue Oct 26, 2021 · 7 comments
Closed

Example of parsing SubMessage data field #509

ethanfrey opened this issue Oct 26, 2021 · 7 comments
Assignees

Comments

@ethanfrey
Copy link
Member

Builds on #502 / #480

Let's show a live example somewhere using these field to parse a SubMessage response. This can be only in test code, maybe in multitest. Best if used in production code. Maybe rust doc??

Point is something to link to to show how to use SubMessage to instantiate a contract and get it's address.

@maurolacy
Copy link
Contributor

maurolacy commented Oct 26, 2021

After the new cw-plus (v0.10.1) is released, this can be shown by refactoring tgrade-valset to use the new helpers in #480.

Then we can copy / reference that in the docs.

@ethanfrey
Copy link
Member Author

I'd like to update something we have already open sourced, so I can link it this week

@maurolacy
Copy link
Contributor

OK, I can take this after you cut the new release.

@maurolacy maurolacy self-assigned this Oct 26, 2021
@maurolacy
Copy link
Contributor

There's a case in multi-test where prost is currently being used. I'll change that to use the new helpers, and then we can use that as an example if you like / prefer.

@ethanfrey
Copy link
Member Author

Sounds good.
Thank you

@maurolacy
Copy link
Contributor

maurolacy commented Oct 27, 2021

See #515. Example is pretty simple, not sure it will be useful for what you want.

@ethanfrey
Copy link
Member Author

I think it is good enough. At least some working code I can link to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants