Implement contract call type select about contracts-ui HOT 4 CLOSED

Good question. I have less understanding what happens behind the scenes technically. But if the UI can tell which message is just a non-payable query and which is a payable transaction, we should indeed change the design here.

from contracts-ui.

i was confused about the use case of this dropdown, it is actually the dry run we were talking about
but, does it make sense anymore as a dropdown?
On the instantiation form we want to display the estimations that come back from the dry run whenever the user changes an input.
We could do something similar here, just show the estimations to the user whenever they type something. But where to display them in the layout? The results panel can be long. With the dropdown approach, they can be shown inside the results panel.
what do you think? @erler @kwingram25

from contracts-ui.

2 new ideas for dispatchables, the getters will only have a read button:

1. display a call button and a dry run button. each button generates a result in the results panel, wether it's a call resul or a dry run result. the dry run happens on click, not as users type
2. display a call button and a predicted outcome panel, similar to the instantiation one but maybe more compact, above the call results panel. the predicted outcome panel will display only the dry run result and will be updated as the user types. in case of unsuccessful dry run, the call button should be disabled, while giving the user meaningful information about what went wrong.

from contracts-ui.

will be done in #297

from contracts-ui.