-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
ipfs key gen
expect mandatorily the optional parameter '-t'
#6861
Comments
It's already the default when initializing the node, we might as well make it the default when creating new keys. fixes #6861
In general, IPFS doesn't have a way to specify "optional" versus "mandatory" flags. However, it makes sense to just make all flags optional (and that's much easier to fix than adding mandatory flags). fix in #6864. |
While the The man page for
That was what I was referring to.
Thanks for the fast fix! |
Yeah, I know. But that help text is auto-generated and fixing it would require either a hack or adding the concept of "mandatory"/"optional" flags to our commands library (non trivial and really not worth it). |
It's already the default when initializing the node, we might as well make it the default when creating new keys. fixes ipfs#6861
It's already the default when initializing the node, we might as well make it the default when creating new keys. fixes ipfs#6861
It's already the default when initializing the node, we might as well make it the default when creating new keys. fixes ipfs#6861
Version information:
go-ipfs version: 0.4.23-6ce9a355f
Repo version: 7
System version: amd64/linux
Golang version: go1.13.7
Description:
The help states, that '-t' is optional:
But running key gen without '-t' fails:
The text was updated successfully, but these errors were encountered: