-
Notifications
You must be signed in to change notification settings - Fork 28
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
Import statements in golang should be ignored #365
Comments
Having the same issue, I noticed there is a piece of code that is supposed to do this but apparently it does not work as expected:
I tried to come up with my own filter but with no success - is there a known workaround? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I often get warnings in my golang projects that my import blocks are duplicates and should be refactored. Unfortunately, that's not how golang works - everything a file references must be imported, there are no transitive imports.
A codeblock like:
Will often occur in many files and the only way to get rid of duplication would be to put everything in one file which is a horrible way to improve maintainability
The text was updated successfully, but these errors were encountered: