fix: correctly decoding string return value#14603
Merged
nventuro merged 1 commit into05-27-fix_allow_of_returning_of_tuples_from_contract_funcsfrom May 29, 2025
Conversation
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Thunkar
approved these changes
May 29, 2025
nventuro
merged commit acb4858
into
05-27-fix_allow_of_returning_of_tuples_from_contract_funcs
6 of 7 checks passed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This pull request addresses an issue where the ABI decoder incorrectly returns string values as numeric byte arrays (e.g., [120n, 121n, 122n]) instead of the expected string ("xyz"). The fix modifies the
AbiDecoderclass to properly parse and convert byte-array-based string representations into their corresponding string literals.Fixes #14600