This repository has been archived by the owner on Jan 16, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 265
Support for vgo aware import paths #558
Comments
Upgrade to 1.10.3 will probably not help with the actual issue because the service does not use |
myitcv
changed the title
Is godoc.org running 1.10.3?
Support for vgo aware import paths
Jun 26, 2018
I've mailed https://go-review.googlesource.com/c/gddo/+/120817 to fix this; would appreciate if someone could please take a look. Thanks |
@shantuo thanks for merging the CL. Is there anything we now need to do to redeploy? |
@myitcv I'll do a redeploy shortly, will report back then. |
The change is live now, thanks for the fix! |
Great, thanks. https://godoc.org/myitcv.io/blah2 now resolves properly |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Edit: retitled to reflect what I'm trying to achieve here, namely minimal support within gddo for vgo-aware import paths.
Is godoc.org running 1.10.3?
Per https://golang.org/doc/devel/release.html#go1.10.minor, 1.10.3 includes minimal support to the go command for the vgo transition. As such it will be essential to correctly resolve any projects/repos that convert to Go modules before the release of Go 1.11.
I ask because the following fails to resolve: https://godoc.org/?q=myitcv.io%2Fblah2
Despite the
<meta>
tags being apparently correct:Thanks
The text was updated successfully, but these errors were encountered: