You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As, many of you already know, in javascript, when using "npm init" command, it asks several questions for project level metadata. Also, developers can add custom commands in "script" section. Some other features like "repository, config" etc.
Can Go have a similar feature when using "go mod init" command? What do you guys think?
Or, in summary, can we have more rich features for go modules?
The text was updated successfully, but these errors were encountered:
It appears to be described here, in particular repository and config. ISTM these are things that just work with Go as part of the go tool, or are part of Go syntax.
We aren't going to add questions to go mod init. In general we've decided that we won't store arbitrary configuration data in the go.mod file. Closing this issue.
As, many of you already know, in javascript, when using "npm init" command, it asks several questions for project level metadata. Also, developers can add custom commands in "script" section. Some other features like "repository, config" etc.
Can Go have a similar feature when using "go mod init" command? What do you guys think?
Or, in summary, can we have more rich features for go modules?
The text was updated successfully, but these errors were encountered: