-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
why does 'cobra init' require --pkg-name when go.mod is present? #891
Comments
That assumes a |
Right. But when it is present (as it was in my case), cobra could use it. |
I don't see any immediate problem with that functionality. If you want to open up a PR with your suggested changes, tag me and I'll take a look. |
Hmmm. Blocked on golang/go#31761, in particular, the addition of golang.org/x/mod/modfile. |
@josharian if this is blocked and has no immediate resolution I think it's appropriate to close this issue. |
As you wish. |
The first line of go.mod contains the fully qualified import path of the module. Could
cobra init
just use it?The text was updated successfully, but these errors were encountered: