-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use real running node instead of emulation #28
Comments
thanks for creating issue @SkymanOne! there are few directions that you touched:
|
What I am saying is the fact that you can have a session in CLI with multiple contracts, selecting a specific contract in the menu and making a call to it is also useful when working with the running node.
No, this is not what I meant. I understand that you can not manually advance blocks in running node, so I think you can limit functionality to just displaying the current block in this case. Overall, my point here is that the TUI you have can be useful when testing contracts on the local testnet. |
ContractsUI does it already with far better UX. If we were to add that feature (i.e. support talking to an actual node) this little tool becomes much more involved as it'd require adding RPC client etc. |
Yes, but that’s an argument for every TUI |
I guess where I am getting at is that it would be cool to have Drink TUI as a TUI wrapper for the |
I think the tool has value beyond emulating pallet-contracts and minimum substrate runtime.
It would be nice to be able to use the tool with an actually running substrate node, as it simplifies interaction with the contract from the CLI (e.g. instantiation, contract calls, etc).
cargo-contract
forces you to specify--suri
and--contract
flags with everycall
commandThe text was updated successfully, but these errors were encountered: