-
Notifications
You must be signed in to change notification settings - Fork 52
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
feat: use commander as arg-parser #859
Conversation
…into commander-refactor
`-e, --ens [<${intlMsg.commands_codegen_options_e_address()}>]`, | ||
`${intlMsg.commands_codegen_options_e()}` | ||
) | ||
.action(async (options) => { |
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.
This manual parsing isn't needed but it seems like there is some issue with commander
parser handler so until it gets fixed, we will be using manual parsing.
Do we still need gluegun, or could we completely remove it? |
Yep but it would be better to do it in other PR. |
Closes: CLI-V1: Refactor, Use Commader (Remove GlueGun) #748
Blocked by: Custom ensName fix for
buildAndDeployApi
#861