You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my case it leads to showing no linting errors while actually there are some and will be shown if I try to start golangci-lint on specific file or if I start binary itself in terminal for whole project.
Unfortunately I cannot share code on which it occurs but I suspect any more-or-less big project with several packages can lead to that behavior.
The text was updated successfully, but these errors were encountered:
Hi @pztrn , if I'm understanding correctly, you are trying to run Analyze - Inspect Code - Whole project?
If that's the case, it's normal as the plugin is designed to run per file. Open a go file then related issues will be highlighted inline.
In my case it leads to showing no linting errors while actually there are some and will be shown if I try to start golangci-lint on specific file or if I start binary itself in terminal for whole project.
Unfortunately I cannot share code on which it occurs but I suspect any more-or-less big project with several packages can lead to that behavior.
The text was updated successfully, but these errors were encountered: