-
Notifications
You must be signed in to change notification settings - Fork 544
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
ux: distinguish public key vs private key in CLI #74
Comments
Hi @ahmetb I would like to provide a PR for this one if u dont mind:) What do u think about switching to cobra for the cli arg parsing? |
I was planning to implement this to get used to the repo, but I’m also noticing a need for using |
Alright I will keep looking then for a chance to contribute |
+1 to someone doing this one! I don't love cobra but could be convinced to switch as long as we don't also bring in viper. |
@FalcoSuessgott are you still interested in trying this? |
@dlorenc implementing that feature or migrating to cobra? |
FWIW I came to terms calling both pub/priv "-key" over time. So I am not sure if this is worth fixing. -key is more friendly than -pub/-priv? |
+1, it's usually unambiguous from the context (e.g. Closing as WONTFIX |
Also we have migrated to Cobra in the meantime. |
Right now
-key
flag is used in both meanings "public key" and "private key".It might be wise to distinguish these as
-key
and-pub
earlier than later. Please vote 👍🏼 👎🏼 .The text was updated successfully, but these errors were encountered: