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

fix: Remove go.mod replace for gno. Use new gnoclient API. #170

Merged
merged 1 commit into from
Aug 29, 2024

Conversation

jefft0
Copy link
Contributor

@jefft0 jefft0 commented Aug 26, 2024

Gno PR gnolang/gno#2641 has been merged, so we don't need the go.mod replace which was introduced in PR #161 .

  • In go.mod, remove the replace and use the latest gnolang/gno.
  • The final gnoclient API which was merged in PR chore: In gnoclient, separate out SignTx and BroadcastTxCommit gno#2641 is different. It uses vm.MsgCall, etc. instead of gnoclient.MsgCall, and uses NewCallTx, etc. instead of MakeCallTx. Therefore, this PR updates api.go to use the new API.
  • Change the helper functions convertCallRequest, etc. to maybe return an error if there is no active account, or if the send amount like "1000ugnot" can't be parsed.

@jefft0 jefft0 requested review from iuricmp and removed request for iuricmp August 26, 2024 10:58
@jefft0 jefft0 force-pushed the fix/remove-replace-for-gnolang-gno branch from 8898a29 to 3825cb0 Compare August 28, 2024 05:50
@jefft0 jefft0 requested a review from iuricmp August 28, 2024 12:23
Copy link
Contributor

@iuricmp iuricmp left a comment

Choose a reason for hiding this comment

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

🚀

@jefft0 jefft0 merged commit 2281464 into gnolang:main Aug 29, 2024
@jefft0 jefft0 deleted the fix/remove-replace-for-gnolang-gno branch August 29, 2024 07:23
Copy link

🎉 This PR is included in version 1.7.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

2 participants