-
Notifications
You must be signed in to change notification settings - Fork 17.5k
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
x/tools/cmd/stringer: Does not work with Go modules #27456
Comments
This falls under issue #24661 |
That is correct. Please subscribe/comment on that issue. It seems there is already an open CL in the works for it. |
I've just been hit square in the face by this:
The funny thing is that this worked perfectly find before I've restructured the codecase, i.e. move pieces to different locations. Its not a problem with the imports per se. |
You are free to comment on the issue. But it is an open-source tool at the end of the day. The best way is to make a contribution yourself :). |
Not being a go internals hacker I was seeing my contribution in highlighting that the efforts for fixing stringer as far as this and the tracking issue are concerned have come to an apparent stop and the tracking issue might not be enough to gain traction. |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.11 linux/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?What did you do?
I executed
stringer -type=Field,FieldName -output=constant_string.go
to generate strings for the following file:There is another file in the package that imports
golang.org/x/text/collate
, but it does not need any strings generated.What did you expect to see?
Stringer works correctly
What did you see instead?
The text was updated successfully, but these errors were encountered: