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

Create configurable groups of lints #835

Open
suaviloquence opened this issue Jul 26, 2024 · 0 comments
Open

Create configurable groups of lints #835

suaviloquence opened this issue Jul 26, 2024 · 0 comments
Labels
C-enhancement Category: raise the bar on expectations

Comments

@suaviloquence
Copy link
Contributor

Describe your use case

With the addition of lint-level config, it would be helpful to have lint groups that you can configure many similar lints at once with one config entry. For example, given a group of suspicious lints that are warn-by-default (to prevent false positives), some users want to make them all deny without having to list every single lint.

Describe the solution you'd like

The ability to configure something like

[package.metadata.cargo-semver-checks.lints]
suspicious = "deny"

(of course, both level and required-update can be configured, just like an individual lint)

Alternatives, if applicable

We need to think about whether we want one group per lint (like in clippy) or multiple. Having just one would be less complicated to implement, but if we had multiple, we could have (e.g.), a group for all the different kinds of #[must_use] lints as well as all minor-by-default lints (which tokio wants?). We would also have to think about priority of configuring groups vs configuring lints. Cargo [lints] has a priority key, for example.

Additional Context

No response

@suaviloquence suaviloquence added the C-enhancement Category: raise the bar on expectations label Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement Category: raise the bar on expectations
Projects
None yet
Development

No branches or pull requests

1 participant