-
Notifications
You must be signed in to change notification settings - Fork 154
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
Resolve redundancy of contract deployment #555
Comments
Good shout, although I found that in between txs I had to pull fresh gas fee data to get it to work, so if we were to make an object like: const deploymentOptions = {
maxFeePerGas: gasFees['maxFeePerGas']
} we would need to re update the object value every time we pull fresh data :/ Will need to think how to clean up that code |
|
I think this can be unified in the cli. There might be reasons why one would only want to call one function at the time. Or maybe have a deployAll function as well that calls all of them |
Had thought to solve it by something like following:
|
Nice this would definitely work |
oh I intended to make just one function like following and call it from business logic:
It would get rid of 50+ lines lol |
yea that's perfect will implement later |
We need to add the
|
Refactored deployment scripts to be more concise fix #555
Refactored deployment scripts to be more concise fix #555
Originally posted by @gurrpi in #553 (comment)
The text was updated successfully, but these errors were encountered: