Skip to content
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

Add option to pass parameters in contract deployment #111

Open
csmuller opened this issue Jun 30, 2021 · 3 comments
Open

Add option to pass parameters in contract deployment #111

csmuller opened this issue Jun 30, 2021 · 3 comments

Comments

@csmuller
Copy link

The visual tracker allows to deploy contracts via the GUI. Though, contracts that expect a data parameter in their _deploy method can't be handled correctly, since it is not possible to pass a parameter via the visual tracker's GUI. Thus, this issue asks for the option of passing parameters in the process of deploying a contract with the visual tracker.

@robliou
Copy link

robliou commented Jun 4, 2022

I'm assuming this issue still hasn't been addressed, correct? I tried getting it to work on my own setup but was unsuccessful...? @devhawk

@devhawk
Copy link
Contributor

devhawk commented Jun 4, 2022

This has not been addressed to my knowledge

@mialbu
Copy link

mialbu commented Apr 6, 2023

This would be a really convenient feature imo. When developing a contract with deployment data, developers currently are forced to use an SDK to deploy the contract. I rewrote the example in neow3j's boilerplate, hardcoding an address instead of passing it in the deployment, so that developers can more easily get started with the boilerplate and the visual devtracker together. It would be awesome if this option was provided to showcase new developers in a more convenient way that something like this does not need to be hardcoded in the contract, but can just be passed when deploying.

It's been a while since this issue was opened, @devhawk do you think this could get some priority in the near future?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants