You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 12, 2022. It is now read-only.
We have a bunch of method data available that we are not rendering as well as we could.
In this screen shot, on the right we have a contract we know nothing about, and on the left we have one where we know a lot!:
Unfortunately, we've chosen to display what we know in a nearly useless way. What we know:
The method is named Swap Sai To Dai (displayed well)
The method has one parameter, a uint256, and we know its value!!!
Rather than showing
Parameters:
[
{
"type": "uint8"
}
]
Which looks like we don't know anything about it, why could show something as useful as:
# Swap Sai to Dai
Parameters:
- uint256: 20000000
Where the number 20000000 could be user-editable, and more!
If the label uint256 looks useless to you, that's probably because it's programmer talk for "number". We probably don't even need a label. We don't know the name of this value, we just know it's a number, so we could display a number in place here.
In fact, we know the type of every parameter that comes through, and we know what those parameters are, so we could display meaningful representations of many things!
For example: One type is address. This is an opportunity where we could show an icon, a name, link to a block explorer, all sorts of stuff! But today, there's not even an easy way to tell which part of the HEX DATA at the bottom is the address.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have a bunch of method data available that we are not rendering as well as we could.
In this screen shot, on the right we have a contract we know nothing about, and on the left we have one where we know a lot!:
Unfortunately, we've chosen to display what we know in a nearly useless way. What we know:
Rather than showing
Which looks like we don't know anything about it, why could show something as useful as:
Where the number
20000000
could be user-editable, and more!If the label
uint256
looks useless to you, that's probably because it's programmer talk for "number". We probably don't even need a label. We don't know the name of this value, we just know it's a number, so we could display a number in place here.In fact, we know the type of every parameter that comes through, and we know what those parameters are, so we could display meaningful representations of many things!
For example: One
type
isaddress
. This is an opportunity where we could show an icon, a name, link to a block explorer, all sorts of stuff! But today, there's not even an easy way to tell which part of theHEX DATA
at the bottom is the address.The text was updated successfully, but these errors were encountered: