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

CAP-58: Support deploy with constructor arguments #1561

Closed
leighmcculloch opened this issue Aug 25, 2024 · 0 comments · Fixed by #1574
Closed

CAP-58: Support deploy with constructor arguments #1561

leighmcculloch opened this issue Aug 25, 2024 · 0 comments · Fixed by #1574
Assignees

Comments

@leighmcculloch
Copy link
Member

CAP-58 is in protocol v22 and adds support for calling a constructor as part of the deploy process.

From the CLI's perspective this means that the deploy can have required parameters same to how an invoke can have required parameters. So the ability to use the contract interface to determine which parameters are required is needed on the deploy command.

Ideally the deploy command works the exact same way the invoke command does. Using the -- -h syntax should show the help for the constructor, and the parameters for the constructor should be passed after the --.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
3 participants