-
Notifications
You must be signed in to change notification settings - Fork 386
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
importpath set only to package name, rather than full path (due to proto go_package option) #124
Comments
It seems like there may be a strong correlation between there being a |
Yeah, this appears to be directories that have a option go_package = "api"; It seems like gazelle is now using this verbatim instead of trying to resolve to the full path? |
oh neat, the recommended value for |
Thanks for investigating and fixing this. I didn't know about the package name form. I wish there were better documentation for this on golang/protobuf. |
I'm attempting to update kubernetes/kubernetes to a more recent version of rules_go, and due to the warnings about
importpath
deprecation, decided to update gazelle as well, from 31ce76e to 683e26c.Gazelle removes the
importpaths
outsidevendor/
, and correctly preserves most of theimportpath
s invendor/
, but a number are rewritten to include only the package. For example, some of the incorrect diffs look likefull diff: importpath-diff.txt
Note that kubernetes/kubernetes is a little weird, in that we have a
staging/
directory which is really vendored code (intended for other kubernetes/ repos), but we symlink to these directories fromvendor/
to make go happy. Gazelle basically handles these correctly, though we have a post-gazelle sed to fix theimportpath
s. I don't think that's affecting what's happening here, though, since these packages are incorrectly filled even without the sed, and it's affecting some of the normal vendored dependencies too.The text was updated successfully, but these errors were encountered: