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
There are a lot of users getting stuck during the getting started documentation or shortly thereafter. Some of the issues include:
User installs both gqlgen globally (and probably gets master), then installs gqlgen from dep. So generated code is no sometimes not compatible depending on the state of master.
Users trying to execute gqlgen outside of their GOPATH. We should at least make this clear that it's not currently possible and why.
User cannot find gqlgen binary — some people are struggling binding the binary, either they don't have it in their PATH, or have another configuration error.
We should address these issues and ensure that the described path does not easily run into any of them.
The text was updated successfully, but these errors were encountered:
Can someone PLEASE tell me how to be "in the GO PATH"? I have tired everything I can think of and get the same message, and have searched until I am blue in the face and can not see a clear answer anywhere. I have tried setting GOPATH to various places, and tried CD'ing to where it seems to be and it never changes the results. gqlgen gets installing into ~/go/bin/ on the Ubuntu instance I have tried it on (also tried the same things on Mac).
There are a lot of users getting stuck during the getting started documentation or shortly thereafter. Some of the issues include:
User installs both gqlgen globally (and probably gets
master
), then installs gqlgen from dep. So generated code is no sometimes not compatible depending on the state of master.Users trying to execute
gqlgen
outside of theirGOPATH
. We should at least make this clear that it's not currently possible and why.User cannot find
gqlgen
binary — some people are struggling binding the binary, either they don't have it in theirPATH
, or have another configuration error.We should address these issues and ensure that the described path does not easily run into any of them.
The text was updated successfully, but these errors were encountered: