Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Interface: getting names/types of inputs and outputs of a given function.
See original GitHub issueSo this is a suggestion following from #44…
Since we are now attaching signature and sighash to interface.functions.someFunction I think another logical extension would be to also attach the inputs and outputs arrays from the abi.
This way searching the interface.abi array won’t be needed which would make querying this information easier for any function. Perhaps we’d also want this for the events. It’s also easy to add on to the current implementation since interface.functions.someFunction comes directly from the abi.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The inputs, outputs, signature and sighash of functions and events are now fully exposed. 😃
Thanks!
Hmmm. Maybe I should expose the push-down automata I have in Interface to properly parse brackets into a tree… I will look into whether the current AST data structures make sense outside the library.