You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We also have an open PR to add an osmosis-proto crate to the cosmos-rust repo: cosmos/cosmos-rust#288
Curious what you think about that. I think there's some value in having a monorepo for the Protobuf crates so they can follow a common set of conventions that can evolve together. However, if you have plans for a Protobuf crate, you're also welcome to the osmosis-proto crate and maybe the work in that PR can be opened here instead.
The text was updated successfully, but these errors were encountered:
For osmosis crate, that would be awesome to have! Thanks you for the offer!
For later point about monorepo, it is open for discussion. I have been pondering about it as well. Maybe the generated crate itself can live in different repo due to custom needs and management, but for proto-build, the work we enriching it could become general / customizable tool for generating proto to suites any chain's need. That I think we could contribute back to cosmos-rust. Let me know you thoughts.
The focus here for the moment is to make the type generated works for cosmwasm, and the current our cosmos-sdk is a forked one as well, so we potentially generate cosmos-sdk's type on our own, but let me know if you have better idea on repo management that benefits everyone.
Hi, I own this crate: https://crates.io/crates/osmosis
Would you like it? You're welcome to it.
We also have an open PR to add an
osmosis-proto
crate to thecosmos-rust
repo: cosmos/cosmos-rust#288Curious what you think about that. I think there's some value in having a monorepo for the Protobuf crates so they can follow a common set of conventions that can evolve together. However, if you have plans for a Protobuf crate, you're also welcome to the
osmosis-proto
crate and maybe the work in that PR can be opened here instead.The text was updated successfully, but these errors were encountered: