-
Notifications
You must be signed in to change notification settings - Fork 192
Support named parameter type entry for sc build commands #781
Comments
I'd like to implement this. I would suggest both complete names and some abbreviations, for instance "sig", "bool", "int", "str", "arr" |
👌 |
@LysanderGG go for it! I started investigating yesterday but don't have anything written yet. cc @ixje
I like that it would support both. The original issue was that we didn't want the user to have to remember anything proprietary. My original thought was requiring a list entry (like params for RPC)
With
Also, I was toying with the idea of still supporting the original format. But that is definitely not a must imo. |
I think it might be good to support the old format. There might be old tutorial out there that still use it, or people might prefer it (as it's less typing) |
Current behavior
Do after #623 is merged.
Currently the
sc build_run
andsc load_run
commands require numeric entry of the contract parameter types defined inneo-python/neo/SmartContract/ContractParameterType.py
Lines 29 to 39 in e378012
Expected behavior
We can improve the user experience by allowing for named inputs, such that these numbers don't have to be remembered.
The text was updated successfully, but these errors were encountered: