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

Customise or better default for severity level? #82

Open
lkhphuc opened this issue Mar 9, 2023 · 1 comment
Open

Customise or better default for severity level? #82

lkhphuc opened this issue Mar 9, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@lkhphuc
Copy link

lkhphuc commented Mar 9, 2023

Hi, I found that currently most diagnostics, except for two, are assigned the severity level of "Warning".

It would be nice if this can be customised via user's settings.

Otherwise would you be open to a PR just extending the current behaviour to consider some diagnostic with "Information" or "Hint" level by default like ARG, SIM, PTH?

@lkhphuc lkhphuc changed the title Override severity level. Customise or better default for severity level? Mar 9, 2023
@charliermarsh charliermarsh added the enhancement New feature or request label Jun 16, 2023
@tylerlaprade
Copy link

tylerlaprade commented Jul 22, 2023

I heavily customized flake8 severity levels before switching to ruff, and I had much fewer plugins for it than I use in Ruff: "flake8.severity": {"F": "Error", "E999": "Error", "E": "Warning", "W": "Information", "B": "Error", "C": "Information", "H601": "Information"}

I would like the option to customize the severities as I see fit, preferably in my .ruff.toml, so that I can enforce violations I deem to be Errors to block pull requests in my CI while not blocking on Warnings or below.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants