We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According to The go blog: Using Go modules, go get changes the required version of a dependency (or adds a new dependency).
go get
Since goa gen (or goa example) executes go get at runtime, even if the goa version is specified in the go.mod file, it is ignored and rewritten.
goa gen
goa example
Isn't this behavior causing confusion? There is also a problem that the latest goa specified by the latest commit number can not be used.
before go.mod
module github.com/ikawaha/calc go 1.12 require ( ...snip... goa.design/goa/v3 v3.0.3-0.20190704022140-85024ebc66dc // latest version )
after goa gen/example
$ goa gen calc/design
module github.com/ikawaha/calc go 1.12 require ( ...snip... goa.design/goa/v3 v3.0.2 )
The text was updated successfully, but these errors were encountered:
Thank you for the fix!
Sorry, something went wrong.
No branches or pull requests
According to The go blog: Using Go modules,
go get
changes the required version of a dependency (or adds a new dependency).Since
goa gen
(orgoa example
) executesgo get
at runtime,even if the goa version is specified in the go.mod file, it is ignored and rewritten.
Isn't this behavior causing confusion? There is also a problem that the latest
goa specified by the latest commit number can not be used.
Example:
before
go.mod
after goa gen/example
$ goa gen calc/design
The text was updated successfully, but these errors were encountered: