desmos-labs / contracts-bindings Goto Github PK

Feature description

Add binding to performs the revers search of app links and chain links.
See Desmos issue: desmos-labs/desmos#793

Currently there's some missing bindings and some outdated bindings for the x/subspaces module.

Missing:

• MsgCreateSection
• MsgEditSection
• MsgMoveSection
• MsgDeleteSection
• MsgMoveUserGroup

Outdated:

• MsgCreateUserGroup
• MsgSetUserGroupPermissions
• MsgSetUserPermissions

At the moment a lot of public methods are not documented making very hard for a developer understand what a function does

The last week Conf.io released CosmWasm v1.0.0 🎉.
I think now we can update the bindings deps towards this version:
https://github.com/CosmWasm/cosmwasm/releases/tag/v1.0.0

Currently it looks like the MsgUnlinkChainAccount is not supported in the bindings.
We should implement it as well.

Feature description

Add to ProfilesQuerier, RelationshipsQuerier, SubspacesQuerier the ability to provide paginated data as a sequence of elements using PageIterator.

I see that we have some MsgBuilder structs that are empty and are used to easily create msgs that can be sent to the chain.
Since all of the methods exposed from that structures can be converted to static methods I suggest to remove all the MsgBuilder structs and move their methods to the corrispettive enums.

For example al methods of ProfilesMsgBuilder can be moved into the ProfilesMsg enum like this:

impl ProfilesMsg {

     pub fn save_profile(
        dtag: &str,
        creator: Addr,
        nickname: &str,
        bio: &str,
        profile_picture: &str,
        cover_picture: &str,
    ) -> ProfilesMsg {
        ProfilesMsg::SaveProfile {
            dtag: dtag.to_owned(),
            nickname: nickname.to_owned(),
            bio: bio.to_owned(),
            profile_picture: profile_picture.to_owned(),
            cover_picture: cover_picture.to_owned(),
            creator,
        }
    }
   
   // Other functions....
   
}

Please let me know what you think about this @bragaz @dadamu.

After submitting the crate to crate.io create a template like cw-template to help developers starts creating smart contract that needs to use Desmos messages.