feat: add contract-write functionality #210
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Support for boolean, string, array, and payable argument types - Improved error messages for invalid or empty input values
…ture - Documents new write support, robust argument handling, improved UX, and error feedback in the contract command. - Includes usage and concrete contract examples.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request: Add Contract Write Functionality & Improve Documentation
Summary
This PR introduces:
The
contractcommand now supports both reading from and writing to smart contracts, allowing users to interact with write functions directly from the CLI.The new
README-contract-write.mdprovides a clear, prioritized summary of the write feature, including usage examples, input validation, error handling, and explorer link features.Motivation