-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
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
fix:complex calls #31
Conversation
Add tests for the `m.call(...)` function in core.
Don't block validation on overloaded functions invoked with args i.e. `example(uint256,bool)`.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Repeating here what I said to John in the chat just for the record: I think using the signature like this is fine, and that the alternative of trying to use the value of the |
I have the following module:
And I am getting this error:
But when I changed it to the function I want to execute (
How can I execute that function? |
Can you paste a version of the Solidity code of your contract? Are you able to invoke the |
The version of Solidity I am using is |
@kanej based on this issue, it looks like there is a bug with Ignition dealing with any |
Kindly please see to it, @kanej. Thanks. |
To allow
m.call(...)
calls against overloaded functions we now support the following syntax:Technical details
The invocation using the
setAddr(bytes32,address)
was fine, but failed the initial validation. This fix is to the validation code.