Implement contract message/constructor arguments about contracts-ui HOT 3 CLOSED

the app already displays an input for each constructor / message argument
they are simple html text inputs at the moment

it's curious that with the current implementation instantiation still works
i am passing the string "false" to flipper's new constructor and the value is converted by the api
same for erc20 where i pass a number as string
maybe we don't need to convert ourselves.

i think we should separate the discussion to:

• validation and type conversion (the field should not be valid unless some criteria, what is the criteria for each type)
• UI for special inputs (dropdown for booleans, how is Balance different from number?)

what would be an example of unsupported type?

from contracts-ui.

Correct that much of the time the string is sufficient, but still it would be ideal to handle each type correctly eventually - dropdown for bool etc. The hardest to support will be structs, enums, and vectors - these are potentially nested. I'm not sure if the JSON-like representation works for these.

from contracts-ui.

closed in #124

from contracts-ui.