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
ABI.parse_specification
outputs
Recently we came across such a contract, where one of the methods (assumeLastTokenIdMatches) does not have an array of outputs in its ABI:
assumeLastTokenIdMatches
// ... { "type": "function", "stateMutability": "view", "name": "assumeLastTokenIdMatches", "inputs": [ { "type": "uint256", "name": "lastTokenId", "internalType": "uint256" } ] }, // ...
If I try to parse this ABI using ABI.parse_specification, the function assumeLastTokenIdMatches is skipped:
iex(1)> File.read!("contract-abi.json") |> Jason.decode! |> ABI.parse_specification |> Enum.filter(fn %ABI.FunctionSelector{function: name} -> name == "assumeLastTokenIdMatches" end) []
contract-abi.json
Possibly, the problem is somewhere here:
ex_abi/lib/abi/function_selector.ex
Lines 179 to 183 in 5d63e8a
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Recently we came across such a contract, where one of the methods (
assumeLastTokenIdMatches
) does not have an array ofoutputs
in its ABI:If I try to parse this ABI using
ABI.parse_specification
, the functionassumeLastTokenIdMatches
is skipped:contract-abi.json
Possibly, the problem is somewhere here:
ex_abi/lib/abi/function_selector.ex
Lines 179 to 183 in 5d63e8a
The text was updated successfully, but these errors were encountered: