You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got an EOS smart contract which uses std::optional<std::vector<eosio::name>> as a type of one of its fields. When compiled with AntelopeIO CDT v4.0.1, it produces an ABI which seems to be valid and works fine when deployed to blockchain. However, the abieos lib fails to parse the ABI and throws an "Invalid nesting" error.
Here is a minimum reproducible code to illustrate the problem:
I've got an EOS smart contract which uses
std::optional<std::vector<eosio::name>>
as a type of one of its fields. When compiled with AntelopeIO CDT v4.0.1, it produces an ABI which seems to be valid and works fine when deployed to blockchain. However, the abieos lib fails to parse the ABI and throws an "Invalid nesting" error.Here is a minimum reproducible code to illustrate the problem:
Considering this ABI is valid, would be nice to add support of such nested structures to the lib :)
The text was updated successfully, but these errors were encountered: