-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Add decode function parameters #4917
Comments
@defido Thanks for reaching out to us. I think that will be a nice feature but we will plan it for future releases in 4.x. You are welcomes to contribute this feature for 4.x branch. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment. |
Is there an existing issue for this?
Feature Request
#3016
See here #3016 (comment)
In reference to the this problem people have, decoding a function requires removing the first 8 characters after the 0x.
Adding a decodeFunctionParameters method would solve this, simply by splicing the first 8 characters after the 0x and returning the parameters.
Use Cases
Used in getting the returned parameter data of function calls.
Stops people from being confused about why decodeParameters is not working.
Implementation Ideas
No response
Feature Examples/References
Ugly example, but it works to prove the point.
web3.eth.abi.decodeFunctionParameters([<PARAMETERS>], string)
Final output is CORRECT data.
Are you willing to implement this feature?
The text was updated successfully, but these errors were encountered: