-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
golangci-lint linters should have an output that is formattable #2648
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
Comments
Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors. |
Looked at the guide and this is a general question before implementation |
Hello, Your issue is unclear, can you describe your suggestion a bit more? |
We could
It's just I want to
|
The implementation of this in the run.go is golangci-lint/pkg/commands/run.go Line 467 in d209389
And I raised this issue because the flag was also present on this command (run golangci-lint linters --help for information) |
This comment was marked as off-topic.
This comment was marked as off-topic.
Why do you want to filter the output of |
I meant that
so the local command has the out-format flag, but it's unused |
Why do you want to filter the output of |
I want to run:
|
Why? |
so I can have a dynamic list of the fast ones and run all of them |
ok so you want the behavior described here: #1909 (comment) |
so you would say it's better to:
or the right permutation that is described in the issue mentioned? |
I suppose because you don't provide a clear context, you want to filter on fast linters to be able to run only fast linters on your CI. Note: It's important in an issue to explain the "why" instead of the "how" and provide a clear context, like that we can discuss solutions instead of implementation proposal. |
sorry I just read the contribution guide, and it didn't allow me the section of "Why do you want this change?" felt it was directing me to be explicit on the "how" |
so yes, I wanted to take this command I put up top as a useful one-liner that takes a few seconds to run (based on the codebase) for obvious reasons having all of these linters may be too much, but this might be something useful to drill down and fix :) |
I can close this card as the answer is to "use golangci-lint run" as it's where most of the logic is anyways :) |
Your feature request related to a problem? Please describe.
I wanted to get all of the fast linters, and to do that I need to grep the data I retrieve.
Describe the solution you'd like.
I would want the
--out-format
to be respected here and if it's json it'll output the data in a json structif any other data is provided it'll push a warning it cannot parse in that type and continue with the default output.
Describe alternatives you've considered.
Additional context.
No response
The text was updated successfully, but these errors were encountered: