Closed Viterbo closed 4 weeks ago
Name | Link |
---|---|
Latest commit | 20a536443f9516d40215737848cca3a4a9d09606 |
Latest deploy log | https://app.netlify.com/sites/dev-mainnet-teloscan/deploys/671fc5a5af66d10008ef876f |
Deploy Preview | https://deploy-preview-863--dev-mainnet-teloscan.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Name | Link |
---|---|
Latest commit | 20a536443f9516d40215737848cca3a4a9d09606 |
Latest deploy log | https://app.netlify.com/sites/testnet-teloscan/deploys/671fc5a505fbf0000865b980 |
Deploy Preview | https://deploy-preview-863--testnet-teloscan.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Name | Link |
---|---|
Latest commit | 20a536443f9516d40215737848cca3a4a9d09606 |
Latest deploy log | https://app.netlify.com/sites/teloscan-stage/deploys/671fc5a5abc9aa00083ffcb6 |
Deploy Preview | https://deploy-preview-863--teloscan-stage.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Fixes #487
Description
So far, we could only execute functions that had basic type parameters. With this PR, support is also added for functions with parameters of type tuple or tuple array, of variable or fixed size, using simple inputs where the user must enter a valid JSON format as an array.
For example, a function with an input parameter like the following:
Must be entered as:
This PR includes the Solidity source code of an example contract with multiple functions featuring different parameter types to test various variants and combinations of simple to very complex parameters.
Test scenarios
check this Example Contract on Write section to see test all different types of parameters.
NOTE: The DEBUG button at the side of the Query button is temporal and is meant to help provide a valid input example for each case. So the reviewer doesn't have to deal with writing down a valid input on complex cases. After approval, this DEBUG button (and all associated debug functions) will be removed.