-
Notifications
You must be signed in to change notification settings - Fork 43
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
ex_abi
can't decode string
type
#15
Comments
@ayrat555, could you please clarify your statement? Maybe I missed something, but I see nothing criminal in the decoding of the |
@zergera try setting the latest version of |
@ayrat555, yes, setting version of For ex.:
So we either use
as a As so, I think that it is not an issue of the Of course, a bypass clause can be added to the
but usually this is not the best idea, and it is not related to the As so, I suggest to close this issue and continue this discussion in the blockscout/blockscout#1546. |
@zergera I think |
At the moment, your library follows the letter of the specification, except for the decoding of the
is the encoded representation of the value And
is the encoded representation of the value If you'll try to decode the second byte sequence as a value of type
will be interpreted as a byte length of the following string (
as a string itself.
will be considered as the next data piece. If you decide to change the decoding behavior, you will rely on the existence of this tail ( |
@zergera can you please create PR in blockscout fixing all errors? |
@ayrat555, quick fix is blockscout/blockscout#1824 . |
Decoding of string types fixed in |
The issue is related to the latest PR (#14). Now data byte length is not considered for
string
type (maybe for some other dynamic types)The text was updated successfully, but these errors were encountered: