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

cosmos-sdk-rs v0.1.1 #78

Merged
merged 1 commit into from
Apr 14, 2021
Merged

cosmos-sdk-rs v0.1.1 #78

merged 1 commit into from
Apr 14, 2021

Conversation

tony-iqlusion
Copy link
Member

Initial release under the cosmos-sdk crate name.

@tony-iqlusion
Copy link
Member Author

PTAL at #77 as well and let me know if you have any comments before a release.

Comment on lines +6 to +12
//! ## About
//!
//! This library is presently designed to serve as a *client* for interacting
//! with the Golang implementation of the Cosmos SDK.
//!
//! It does not implement server-side functionality (yet), such as hooks
//! and message passing.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a small description of the initial goals of this library.

@tony-iqlusion
Copy link
Member Author

Unfortunately it's not possible to change the hyphenation of a crate once published. See:

rust-lang/crates.io#728

   Uploading cosmos-sdk v0.1.1 (/Users/bascule/src/cosmos-rust/cosmos-sdk-rs)
error: api errors (status 200 OK): crate was previously named `cosmos_sdk`

However the crate can still be imported as cosmos-sdk if desired.

I guess I will publish under the cosmos_sdk name for now and we can potentially revisit this if people are bothered by the inconsistency of the underscore.

@tony-iqlusion tony-iqlusion merged commit 98e0144 into main Apr 14, 2021
@tony-iqlusion tony-iqlusion deleted the cosmos-sdk/v0.1.1 branch April 14, 2021 16:49
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

Successfully merging this pull request may close these issues.

2 participants