-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
way to identify newly available linters #1686
Comments
Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors. |
Currently, you can find this information on the following pages: |
@ldez Hi -- yes, I know that Then, magnify this times the number of projects one has these settings / configs for. IMO, the older (but deprecated) method of being able to pin to a specific version's linters (and disabling unwanted ones explicitly) was easier to work with. |
Personally, I like I think that an enhancement can be made in the linters manager by adding a golangci-lint/pkg/lint/lintersdb/manager.go Lines 109 to 359 in 60455b5
and add a new flag or subcommand to the |
Me too! I don't have the reference handy, but I believe it's been made pretty official and is documented somewhere on the main site, but let me know if I'm wrong on that!
Like this idea! |
For what its worth, I also use Is there any links to why |
https://golangci-lint.run/usage/configuration/
which comes from Lines 66 to 67 in 1221939
added in #803 |
Maybe it would be worth adding an enable-new command that adds any unmentioned linters to the config file. While I liked using enable-all, I can see why it would be annoying for someone just trying to upgrade to a new version of golangci-lint that supports a new go version, for example. |
I also use |
I added a https://golangci-lint.run/usage/linters/ I have an idea for a command line approach but I need to think more about it. |
Nice work, thanks. |
I would like to (re)open the debate about the deprecation of So please describe your use-cases in this new issue. |
Is your feature request related to a problem? Please describe.
Just curious - given the deprecation of
enable-all
(e.g., #542 (comment)), is there any way to find out what linters are newly available, shy of comparing the list of enabled ones to the full list on the site?It would be extremely useful if there were an option to print available (but not enabled) linters. Also, it's great that golangci-lint supports a lot of different types of linters, but sometimes it could be more clear which ones are recommended for typical use cases, so some kind of opinionated preset would also be nice.
IMO, the recommendation it seems is being made (to explicitly list all linters by name one by one in each project's config) is a bit of a hassle / maintenance headache.
Describe the solution you'd like
A couple options - one would be a command line flag to print all available, but not enabled linters based on the current version of the tool and the current project's config.
Optionally, some other way to restore the previous behavior of allowing one to move to a more "disable explicit" mode and / or some kind of "recommended" config that would continue to add the most useful of new linters automagically.
Describe alternatives you've considered
Some kind of way to define an org-wide preset (similar to tools like, say,
eslint
for node) might be interesting.Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: