Open joshtharakan opened 1 year ago
Thanks for reporting this. I will look into it when I get some cycles. It should generate a unique pathname
for each overload to give you a distinct endpoint for each one. Clearly the converter is not doing this as expected though, so thanks for reporting this.
EVM based blockchain has the capability to overload methods with different signatures. While converting the ABI of those methods into FFI, I have found that overloaded methods are not properly converted and only the first reference is converted into FFI representation.
Steps to reproduce Call the
POST
/contracts/interfaces/generate
endpoint with the following payload:Actual outcome
Here the two other signatures for the method
sendGreeting
is ignored.