-
Notifications
You must be signed in to change notification settings - Fork 812
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
[contract-call-view] Add contract-call-view
Strategy
#1382
Conversation
contract-call-view
Strategycontract-call-view
Strategy
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.
Hi @tkowalczyk contract-call
strategy already accepts a param output
@ChaituVR you are right but |
@tkowalczyk Could you add a new param on |
@ChaituVR to be honest it will require to rewrite the |
@tkowalczyk Did you try something like here |
@ChaituVR , Yes of course... I am not able to deal with contract-call with function which return more than 1 value in the response:
and when I specify only one return value I got the value but for the first one not the one I provide
|
For the playgrounds links you have provided, try adding |
Sorry but I dont get it, link that you have provided does not work, what do you mean by adding |
I mean like this: {
"address": "0x5cA0F33f1ebD140def87721291FF313A9141F79e",
"output": "1",
"methodABI": {
"inputs": [
{
"internalType": "address",
"name": "",
"type": "address"
}
],
"name": "userInfo",
"outputs": [
{
"internalType": "uint256",
"name": "lastStakeTime",
"type": "uint256"
},
{
"internalType": "uint256",
"name": "amount",
"type": "uint256"
},
{
"internalType": "uint256",
"name": "waitingRewards",
"type": "uint256"
}
],
"stateMutability": "view",
"type": "function"
}
} |
It looks ok |
Thanks for testing @tkowalczyk it is just to avoid similar strategies :) hope you understand, so closing this PR for now. feel free to reopen if you need it |
Changes proposed in this pull request:
contract-call