CosmWasm smart contract hooks

[bigs]

Description

This closes feature request #50.

First, want to highlight that the primary author of this change is @BurntVal and that my role has merely been to review, give advice, and liaise!

This PR introduces four hooks for interacting with CosmWasm smart contracts in React applications. They are:

• useInstantiateContract—a mutator to instantiate a smart contract with a message provided by the caller.
• useExecuteContract—a mutator to execute a smart contract, passing it a message provided by the caller.
• useQueryRaw and useQuerySmart—Hooks to query the state stored within a smart contract.

We made our best effort to follow the style and standards of the graz codebase. We generally made an effort to keep the typing as strong as possible, so the mutators are all parameterized by input and output types.

Checklist

• I have made sure the upstream branch for this PR is correct
• I have made sure this PR is ready to merge
• I have made sure that I have assigned reviewers related to this project

Changes

• Added useInstantiateContract hook
• Added useExecuteContract hook
• Added useQuerySmart hook
• Added useQueryRaw hook

Screenshots

n/a

Testing

To test our changes, we locally extended the sample project in templates/default to include queries and transactions made to various sample contracts using all of the hooks added in this change request. Through testing in this application setting, we confirmed instantiation, execution, smart queries, and raw queries all worked.

Links/References

• CosmWasm
• @cosmjs/cosmwasm-stargate

Notes

• In order to make the hooks flexible, many of the hook arguments are optional (in the event that they are not yet known at first component render). In these instances (in the queries, specifically), the hooks will be automatically disabled until they are present to avoid invalid queries.

[bigs]

@codingki This is ready for a review! I'm not sure what's failing in the graz-example deploy, as I've not got permissions to view the project on Vercel.

[codingki]

Dont mind the failing builds, we are currently working on it get it fixed @bigs

[codingki]

Awesome work @bigs🔥 Thanks for working on this, We are really appreciate your work🫡
There are some comments that needs to be resolved and suggestions before merging💪

[codingki]

In order to make the hooks flexible, many of the hook arguments are optional (in the event that they are not yet known at first component render). In these instances (in the queries, specifically), the hooks will be automatically disabled until they are present to avoid invalid queries.

We can make the hooks params optional and have a enabled options on the query options

[BurntVal]

@codingki The requested changes were implemented and is ready for review again :)

[codingki]

Looks good to me! found couples suggestion non blocking the merge. Great job🫡

[BurntVal]

Sorry for any inconvenience. It's the little things that always escape my mind. That should be everything now :)

[codingki]

Awesome🔥

[codingki]

These will be included in 0.0.28 and up

[BurntVal]

Awesome. Thank you guys for the support and quick responses!