-
Notifications
You must be signed in to change notification settings - Fork 315
fix(lazer) Lazer upgrade contracts script fix #3270
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
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| "std-output": { | ||
| type: "string", | ||
| demandOption: true, | ||
| demandOption: false, |
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.
why did you change this and added a check in another place?
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.
plus 1 to this question. Yargs handles this for you. It also provides you a way to customize the error message if the argument is not provided
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 don't need "std-output" in the upgrade_evm_lazer script.
Summary
Rationale
How has this been tested?