-
Notifications
You must be signed in to change notification settings - Fork 23
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
envy.Mods() - Modify behavior to better match the current module auto… #25
Conversation
This PR says, regardless of what you've set |
@markbates ahh right, let me fix that. |
@markbates yeah I'm not sure how to say that we support go modules auto detection if GO111MODULE is unset but not if GO111MODULE=auto. I just removed that text but I can replace if it you have suggestions. I pushed to kick off the automated tests. I'll look into what is going on there. |
@markbates ready for re-review, tests are passing. |
Can you please write some tests? Also, what if “auto” is set, which is the Go default, and I’m outside the GOPATH? It should work, but I don’t think it will. Thanks. |
@markbates I think I addressed the issue with setting GO111MODULES to 'auto' and added a few obvious tests. Thoughts? |
Sorry for the delay. The logic feels a little strange to me. Perhaps something like this:
|
@markbates yeah that is a more simple way to put it, let me fix up and repush. |
…detection in place in go Add tests for GO111MODULE being set to auto or being left blank.
Hi @markbates, any other comments or fixes you’d like me to make to this pr? |
I’m at a conference right now, but I will look at this on Monday.
…-----------
Mark Bates
On Apr 12, 2019, 8:14 AM -0400, Chris Morgan ***@***.***>, wrote:
Hi @markbates, any other comments or fixes you’d like me to make to this pr?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
…detection in place in go
Combined with packr2 this fixes an issue I was seeing with incorrect imports in main-packr.go.
This hung me up for a few hours today and may be the reason some others have ran into the same thing. The go devs have changed the module support to autodetect I think in 1.12 and imo we may want to keep pace with that as its what people are expecting to see.
We could also improve this to only perform this auto detection if using 1.12 (or whatever version introduced the auto module support) if it is important to maintain behavior.