data-dh-property-method-id
This is the id
that was set when we created our Method Instance. This needs to match exactly so that the DappHero engine knows that this input is intended for that method instance. data-dh-property-input-name
This is the name of the argument for the method that you are trying to interact with. This must match the name defined in the Smart Contract ABI data-dh-property-input-name
would be bar
. This is how we link the input field on our website with the input argument required by the smart contract. It needs to match for the DappHero engine to know where to put the input data!auto-clear
tag to the input to explicitly tell the DappHero engine if you want the form value to be cleared after invocation. data-dh-property-auto-clear="false"
to tell DappHero to not clear your input after a user clicks 'invoke'. proposalNameArray
or proposalNameMapping
. data-dh-property-input-name
to access their values. data-dh-property-input-name="$true"
is scheduled to be deprecated at some point in the future. For now, continue to use it, but check back regularly to learn when we will plan the change. mapping
of a mapping
.{"constant":true,"inputs":[{"name":"","type":"address"},{"name":"","type":"address"}],"name":"allowance","outputs":[{"name":"","type":"uint256"}]
name
value of empty string: ''
. To access these we have recently introduced array indices notation. To access the the first argument (The outer address mapping) you would use the following tag: bytes32
and ascii
as well as ether
and wei
.ascii
(ASCII is the standard way of entering normal text) but DappHero will convert it to bytes32
before sending it to the contract.data-dh-property-method-id
<<aUniqueString>>
data-dh-property-input-name
<<input name>> || $true
data-dh-property-auto-clear
false || true
data-dh-modifier-display-units
ether
wei
bytes32
ascii
data-dh-modifier-contract-units
ether
wei
bytes32
ascii