Skip to content
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

Sort by linter and not just line number #4197

Closed
x528491x opened this issue Nov 13, 2023 · 1 comment · Fixed by #4467
Closed

Sort by linter and not just line number #4197

x528491x opened this issue Nov 13, 2023 · 1 comment · Fixed by #4467
Labels
area: output Related to issue output enhancement New feature or improvement

Comments

@x528491x
Copy link

Your feature request related to a problem? Please describe.

When using the CLI with --sort-results, it only sorts by line number. I usually run --enable-all and to catch all lint errs and I want to be able to sort by linter in an alphabetical order. Even using the tabbed output format is not straightforward because the spaces between the columns are arbitrary and not an actual single tab.

Describe the solution you'd like.

An inbuilt --sort-results-by-linter would be great.

Describe alternatives you've considered.

golangci-lint run --enable-all --out-format=tab | sed "s/ \+ /\t/g" | sort -t" " -k2

Additional context.

No response

@x528491x x528491x added the enhancement New feature or improvement label Nov 13, 2023
Copy link

boring-cyborg bot commented Nov 13, 2023

Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors.

@ldez ldez added the no decision No decision to fix or not label Jan 19, 2024
@ldez ldez added area: output Related to issue output and removed no decision No decision to fix or not labels Mar 8, 2024
@ldez ldez closed this as completed in #4467 Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: output Related to issue output enhancement New feature or improvement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants