We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
在solc中,会自动生成Java代码,其中每个event会生成一个对应的内部类PO,以EventResponse结尾,例如存在合约:
event LogSetSArray(uint256[2] o, uint256[2] n);
对应的java代码为:
public static class LogSetSArrayEventResponse { public Log log; public List<BigInteger> o; public List<BigInteger> n; }
但是,在最新的版本中,如果event中存在动态或静态数字的数组,会统一映射为 List,但是实际上的类型并非 List。
以上述类型为例,当调用时,实际的类型为原版本的映射类型,
List<LogSetSArrayEventResponse> LogSetSArrayEventResponseList = contract.getLogSetSArrayEvents(receipt);
实际的类型为List:
[{"value":1,"typeAsString":"uint256"},{"value":2,"typeAsString":"uint256"}]
这个问题会导致下游系统对数据的解析产生错误。
The text was updated successfully, but these errors were encountered:
No branches or pull requests
在solc中,会自动生成Java代码,其中每个event会生成一个对应的内部类PO,以EventResponse结尾,例如存在合约:
对应的java代码为:
但是,在最新的版本中,如果event中存在动态或静态数字的数组,会统一映射为 List,但是实际上的类型并非 List。
以上述类型为例,当调用时,实际的类型为原版本的映射类型,
实际的类型为List:
这个问题会导致下游系统对数据的解析产生错误。
The text was updated successfully, but these errors were encountered: