-
Notifications
You must be signed in to change notification settings - Fork 2
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
Test add program task #32
Conversation
Could you rebase this PR? |
66e3b19
to
bb5a195
Compare
Done ✨ Awaiting review |
This is cool! I worry we're entangling our tasks too much with hardhat-deploy, but I don't mind it. |
task("add-program") | ||
.addParam("aludelFactory", "address of the aludel factory") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could use these tasks for locally deployed contracts, and it would be helpful to overwrite deployed addresses.
I think we need to leave it as an optional param
the idea behind this is to have the deployments saved in the
If you deploy the contracts locally, then If it's the case that you want to use the tasks on a different deployment, then I feel that being able to use the scripts on addresses that are not registered |
it's meant to log on standalone task runs, but not pollute the test output
bb5a195
to
10a7239
Compare
well, some of it at least
4bf7a07
to
51d0cbd
Compare
- cleaner logs - default startTime is now as requested by joeh some time ago - template is mandatory - use AludelFactory from deployments
51d0cbd
to
8213523
Compare
merge after #31
Main idea behind this PR is to have early feedback on how I'm testing the tasks before tackling all of them, especially the one to launch an aludel.